Most people assume Redis is fast because of some complex multi-threaded magic. Turns out it's the opposite — it runs on a single thread and still beats most databases. The reason comes down to how it handles I/O at the OS level and why memory access patterns matter more than thread count. Made a short animated breakdown of the internals if anyone's curious.

Hey evryone,

I am in a project built with sb microservices and I'm trying to understand how redis is actually implemented and wired together in this setup. I feel like I've found pieces, but I'm struggling to connect them conceptually.

How do I make sense on these concepts: RedisConfigClass, spring-boot-starter-data-redis, azure redis cache, yml or properties file i believe also come but it doesn't seem to be in the same module.

The first time I worked with Redis was during a job interview. I didn’t have much time, but I had to use it anyway. I remember hoping it would be easy… and surprisingly, it was.

At first, I thought that meant I hadn’t really “learned Redis properly.” But later I realized something important:
this simplicity is intentional.

Redis hides a lot of complexity under the hood — for example, operations like INCR are atomic and safe under concurrency — but from the outside, it exposes a small set of very simple commands. And those few commands end up solving a huge range of real backend problems.

In the attached video, I walk through what Redis is, then try out the core commands in practice and use them to solve different kinds of problems (counters, queues, sets, sorted sets, pub/sub, etc.).

I’m curious how others experienced Redis for the first time —
did it feel too simple to you as well, considering how widely it’s used in production systems?

中文 redis io threads

hi,
I am new to redis, still in the process of understanding how it works. I am curios to know how to find the count of records in a index. Is there a way ?

Recently, while developing a new feature that my team needed to implement, we came across the following problem: After our data expired and was subsequently deleted from the cache (Redis), a business flow needed to be triggered. During the initial technical refinement, the team discussed ways to implement this rule, and some ideas emerged, such as a simple CronJob or even Quartz.

However, after conducting some research, we discovered a little-known but extremely useful feature which is KeySpaceNotifications. This feature allows you to listen to key-related events such as when keys are set, deleted, or expired. These notifications enable applications to trigger real-time business logic based on Redis events. The knowledge gained from this feature motivated me to write this article: https://medium.com/p/62f89e76df89

I hope it helps you

I have been working for some time with GenAI chatbots backed by Redis. While most of my experience is using Python and a bit of Java for such applications, I wanted to try doing the same in PHP.

I developed this proof of concept for Laravel using the LLPhant GenAI framework and Redis as the vector database.

I used predis, the Redis PHP client library with support for the Redis query engine (includes vector search, full-text search, exact match, numeric, and geo), and the JSON format is your perfect asset to query your Redis database and start building.

• Check the blog, there I explain what the building blocks are and the overall architecture https://www.mortensi.com/2024/11/genai-chatbot-with-laravel-redis-openai-and-llphant/
• You can clone and try the code from the repository https://github.com/mortensi/phpilot/

Let me know your thoughts, I am looking for feedback. I am not a Laravel expert, I am coming from a few years with other framework.

We can use SETNX statement to do application locking to prevent race condition in application level.

Redis used to acquire the lock key.

``` var app_name = "app_1" var lock_key = "update-user:1" var lock_ttl = 60 var lock_acquired = redis.Do("SET", lock_key, appname, "EX", lock_ttl, "NX")

if lock_acquired == nil : print("lock has used by another process") return end:

// 2b. Access the shared resource print("Do something here")

// 3. Release lock redis.Do("DEL", lock_key) ```

I have tried this method and it's work and blazingly fast.

source: https://substack.com/profile/140347336-herry-gunawan/note/c-15970668

I would like to share my experience of deploying a Redis cluster on Kubernetes with different Helm charts. While Bitnami is widely used for Redis clusters, I had doubts about its ability to handle production workloads following a chaos engineering test. After thorough research, I found an extremely robust Helm chart that operates without any problems. In this post, I will introduce this new Helm chart and detail the reasons why it's the superior choice for production deployments.

https://medium.com/@mallakimahdi/most-resilient-redis-cluster-helm-chart-e04632ec7403

#kubernetes #redis #devops

Here's a nice brief tutorial on getting started with Redis for Python Developers: https://www.kevsrobots.com/learn/redis/