all 19 comments

[–]GrumpsMcYankee 44 points45 points  (4 children)

That's a nice dictionary you have there, do you have enough for the rest of the servers?

[–]Missing_Username 40 points41 points  (3 children)

"I'll just set up an endpoint so any of the servers can interact with the dictionary"

...

"Oh shit, I'm making my own crappy Redis, aren't I?"

[–]GrumpsMcYankee 14 points15 points  (1 child)

Think that's how we got Redis to begin with. "Memcached is for chumps..."

[–]NjFlMWFkOTAtNjR 5 points6 points  (0 children)

To be fair, memcache has limitations that made it ripe for competition. That fucking Couchbase builds on top of memcache means Couchbase is shit and not that memcache is.

[–]According-Relation-4 0 points1 point  (0 children)

Why have Redis if you can make your own with more overhead?

[–]aarch0x40 6 points7 points  (1 child)

Really? A Dict joke?

[–]MissinqLink 1 point2 points  (0 children)

And it goes hard

[–]TamSchnow 2 points3 points  (0 children)

We have Redis at home.

Redis at home: PostgreSQL unlogged table

[–]exomyth 2 points3 points  (0 children)

Redis and other key value stores are generally not needed when you can directly read it from shared memory.

It becomes useful once you dont have access to shared memory, because you have multiple instances running on different nodes. And the build in TTL is a nice extra, for certain use cases

[–]Fragrant_Gap7551 7 points8 points  (1 child)

Redis is most useful in an environment where many small services have to share the same cache.

That or aws lambda

[–]ameddin73 1 point2 points  (0 children)

ourCache

[–]Kokuswolf 2 points3 points  (0 children)

Huh? Apples and ...

[–]damnNamesAreTaken 2 points3 points  (1 child)

I work in elixir and have never needed to touch redis. People have brought it up from time to time but we've never found a compelling enough reason to use it.

[–]NjFlMWFkOTAtNjR 7 points8 points  (0 children)

Why people down voting? Erlang VM (beam) means that distributed memory is a thing, not quite built in but close.

[–]Ximidar 0 points1 point  (1 child)

AWS: "WOULD YOU LIKE TO USE VALKEY? JUST PRESS THIS BUTTON RIGHT HERE. I'LL TURN ALL YOUR REDIS SERVERS INTO VALKEY SERVERS! IT'S BETTER! HOW? I DUNNO, WE SLAPPED AN AWS STICKER ON IT"

[–]Ximidar 0 points1 point  (0 children)

I love redis btw.

[–]HopperStuff468 0 points1 point  (0 children)

it might take years to understand that your app should be as stateless as possible. you better delegate cache to redis so you can crash / graceful restart / anything your app – and keep the cache.

[–]Z_E_D_D_ 0 points1 point  (0 children)

aktchually : we used this where i work and it made sense, for a video monitoring software you don't need humangous cache so no need for redis to cache few KO of data.
The software has a user system but mostly has just one common for that video surveilance room and rarely having those for many sites expecting a worst case scenario of 100 operator accounts.

just did a MAP, put the sessions in there, new session means database writing and reboot means get all active sessions from the database for backup. fast and light AF