undefined

points

[-]

Yeah I've found this quite odd. Even the LLMs want to pressure you to not use Redis and go all in on Postgres. Postgres is great, and I usually use it. But Redis is so trivial to add to your stack and it does what it does really well. Why not use the right tool for the job?

by c0_0p_1 hours ago|

parent|

[-]

Presumably this is because LLMs just echo all the pro-Postgres Medium articles they've been trained on. They don't have any actual experience.

by happyPersonR2 hours ago|

parent|

prev|

[-]

LLMs from hyperscalers allow for paid advertising

by Faaak2 hours ago|

parent|

prev|

[-]

because if you already have postgres, and dont need thousands of k/v per second, then postgres can do the same ?

by stickfigure2 hours ago|

parent|

[-]

If you're stressing your database, offloading some work to Redis can buy you a lot of Postgres headroom. But sure, start with YAGNI.

by gentlewater1 hours ago|

prev|

[-]

Only problem for me vs using your primary DB is that Redis has no redundancy unless you run it in cluster mode. For us that means when the kubernetes node restarts, availability degrades. Could of course enable clustering, but at that point it isn’t dead simple anymore. And using the DB is.

by preisschild1 hours ago|

parent|

[-]

If you run kubernetes, it might be worth looking at valkey/valkey-operator that manages a valkey cluster for you.

by Xeoncross3 hours ago|

prev|

[-]

Redis really is a great piece of software. Low memory, high-performance, feature-rich, and stable. Really hard to beat it for places where you want a durable cache even if technically you can use something else.

by alex_smart1 hours ago|

prev|

[-]

The problem only arises when you have to worry about persistent state. As soon as you have to worry about that, you have to think about backups, replicas, disaster recovery drills and so on. It is much easier to solve for that can of worms for one system than three.

by deepsun2 hours ago|

prev|

[-]

And Redis has auto-delete rows (aka TTL). In Postgres you need a cron job to clear stale rows.

by pooloo2 hours ago|

parent|

[-]

This is one way to handle the problem, but not the only...

by stavros3 hours ago|

prev|

[-]

Oh no, redis is super simple to set up and use. It's just that setting it up is not as simple as not setting it up.

by tracker12 hours ago|

parent|

[-]

For smaller projects and locally, I'm running background services via a compose file... it's a few lines of configuration, and just works. Redis is crazy low hanging fruit.. even job queues that run over Redis make a bit more sense than with Postgres more often than not.

I'm far more hesitant to throw a more formal MQ in the mix though... mostly from experience in that a lot of mid level ("senior") developers don't really understand queues very well at all. Even if conceptually, using tables for queues is more complex.

That said, I will use PG for workflows similar to K/V, Document (JSONB) and other structures over reaching for say MongoDB, etc.

by willsmith721 hours ago|

parent|

[-]

Of course spinning up a hello world of anything is easy. Now introduce monitoring, change controls, version upgrades, multiple environments and regions

It's not that it's necessarily complex. But if you don't need it, don't use it. The business could use your time elsewhere

by tracker11 hours ago|

parent|

[-]

For a redis cache? I think you're way over-valuing the effort it takes to keep a redis instance running.

For a persistent store.. sure... but that's true for PostgreSQL as well, which has some pretty painful major version migrations by comparison to other options.

by wuliwong3 hours ago|

parent|

prev|

[-]

OK, but it is relatively easy to setup. Obviously, nobody thinks it is _literally_ effortless.

by munk-a2 hours ago|

parent|

[-]

Every extra straw you put on the back of your ops team, especially when you're a young company, adds weight. It's good to be choosey about which technologies actually justify that expenditure.

by wuliwong2 hours ago|

parent|

[-]

Your response is a Strawman argument. I was simply saying that nobody thinks that Redis is literally effortless. I was pointing out that the person's comment was not helpful as they were pointing out that Redis installation does actually require effort.

A better response to my comment could have been "just let it go" or something. ₍₍(˶>ᗜ<˶)⁾⁾

by b-man1 hours ago|

prev|

[-]

I think your post misses the point of the DBMS centralization: managed consistency.

It is not about ops cost in infrastructure, but ops cost in debugging consistency errors.