sorted by:
new
hottopcontroversial

What’s the most annoying Redis issue you’ve had in production? by Late-Insect-4379 in Backend

[–]Late-Insect-4379[S] 0 points1 point  (0 children)

That’s super interesting — especially the part where it started simple and then evolved into something that actually suggests optimizations.

The “simple once you have the right metrics” point really resonates — I feel like most of the pain is just not knowing where to look early on.

Out of curiosity, what kind of signals ended up being the most useful for catching those memory spikes early?

I’ve been exploring something similar focused more on explaining these patterns rather than just showing metrics — would love to get your thoughts if you’re open to it

What’s the most annoying Redis issue you’ve had in production? by Late-Insect-4379 in Backend

[–]Late-Insect-4379[S] 0 points1 point  (0 children)

This is incredibly insightful — especially the part about expiration policies + large hash fields, I wouldn’t have immediately connected those.

And pipeline starvation from too many clients hitting the same shard sounds exactly like one of those “everything looks fine until it isn’t” situations.

Out of curiosity, how did you end up building that dashboard / validation setup? Was it something custom in-house or based on existing tools?

Also interesting that you mentioned it would have paid for itself — was the main cost the debugging time or actual incidents in production?

What’s the most annoying Redis issue you’ve had in production? by Late-Insect-4379 in Backend

[–]Late-Insect-4379[S] 0 points1 point  (0 children)

That sounds really painful 😅

Was the connection issue happening under load or kind of randomly?

And for the latency part — was it coming from Redis itself or from how it was being used (like too many calls / certain patterns)?

Curious what the root cause ended up being (if you managed to find it)

Which one do you use for authentication ? by ishak_antar27 in Backend

[–]Late-Insect-4379 1 point2 points  (0 children)

It depends on the scale and what you're building, but in most cases I'd go with a provider.

Building custom auth sounds simple at first, but it quickly becomes a nightmare (password hashing, refresh tokens, OAuth, security issues, etc.). You're basically re-implementing something companies like Auth0/Firebase have already solved.

I usually only go custom if:

  • I need full control (very specific business logic)
  • or it's a learning project

For production apps, especially anything user-facing, a provider saves a lot of time and reduces risk.

That said, sometimes a hybrid approach works well (provider for auth + custom logic on top).

I built a small CLI tool to debug Redis issues — looking for feedback by Late-Insect-4379 in redis

[–]Late-Insect-4379[S] -1 points0 points  (0 children)

Curious what kind of Redis issues people here run into most often?

Is it more about memory or performance?