←back to thread

The Fastest Redis Ever

(redis.io)
82 points lsferreira42 | 1 comments | 18 Nov 24 21:39 UTC | HN request time: 0.203s | source
Show context
marklubi ◴[21 Nov 24 01:21 UTC] No.42200044[source]▶
This sort of makes me sad. Redis has strayed from what its original goal/purpose was.

I’ve been using it since it was in beta. Simple, clear, fast.

The company I’m working for now keeps trying to add more and more functionality using Redis, that doesn’t belong in Redis, and then complains about Redis scaling issues.

replies(4): >>42201722 #>>42201795 #>>42202030 #>>42202451 #
ivolimmen ◴[21 Nov 24 06:36 UTC] No.42201722[source]▶
This is what I see everywhere. Something is a success and then everybody starts using it wrong. Like Elastic search as database, people use it for searching and then start using it as primary database. Mostly pushed by management BTW not always the software engineer.
replies(3): >>42201736 #>>42201900 #>>42202811 #
1. addisonj ◴[21 Nov 24 07:15 UTC] No.42201900[source]▶
That does not match my experience. Engineers learn a new tool, that tool is successful in solving a problem. Whether it is recency bias, incorrect pattern matching, or simply laziness, the tool is used again but with reduced success. Repeat that process a few more times (sometimes in different organizations) and now the tool is way outside the domain, ill-fit to the task at hand, and a huge pain.

That often happens with engineers who pushed that tool getting promoted a few times and building their career on said tool, which is where I have seen this being pushed down, but I think it is important that in most cases are still engineers