The source code for what follows can be found on Github.
MSETNX when you’re working with a single redis primary node is simple enough to understand: it sets all of the key/value pairs, or none at all. If one of the keys already exists in the cluster, then all of them are rejected.
Sorted Sets in redis are one of my personal favorite tools when operating at scale. As of this writing, there are over 30 unique operations you can perform against sorted sets in redis. This article will focus on some of the more common ones you’re going to need to know, and it will use a reactive lettuce client to demonstrate them.
In the last article, we showed how to do some of the most common single set operations against redis, this article will focus on operating on multiple sets using a lettuce client against redis. Specifically, we’ll focus on subtracting, intersecting, and adding sets. The source code for what follows can be found on Github.
There are, as of this writing, about 15 distinct operations available to someone wanting to work with sets in redis. This article seeks to cover some of the more basic ones using a reactive lettuce client, and a follow up article will seek to deal with explaining some of the more common operations against multiple sets, rather than a single set in this case.
There are about 15 or so commands you can execute against redis for hash types as of this writing. This article will demonstrate some of the more common operations you’re likely to need when using lettuce as your client.
As of this writing, there are a solid twenty or so commands you can execute against redis for the list data type. This article will be walking through some of the more common operations you are likely to need when interacting with redis and lists using lettuce, and the source code can be found on Github.
The source code for what follows can be found on Github.
There are, as of this writing, 27 different string operations available in the redis API. Lettuce appears to have interfaces that directly support all of them.
In clustered redis, any non hash tagged key can be sent unpredictably [well, actually predictably, if you know the formula] to any given primary node in the cluster. The very basic way it works is:
To follow along with this post, it would be best if you have already set up your local redis cluster and know how to connect to a redis cluster and interact with it via Lettuce. And the source code for what follows can be found on Github.
Lettuce has some pretty nice out of the box support for working with clustered redis. This combination–a reactive client and application along with clustered redis–is about as scalable, performant, and resilient as things can get in distributed systems [though there are other tradeoffs which are not the subject of this post].
The source code for this post can be found on Github.
Lettuce supports reading from redis replicas, but with the caveat that it doesn’t [out of the box] provide you with the fine-grained control over when to read from the replicas that you’re likely to want.
In general, you will want to keep your development environment and your higher environments as similar as makes sense [times it doesn’t make sense: when it costs too much], to catch bugs early and often. Here, we’ll quickly run through how to set up a leader/follower topology for redis using docker/docker-compose on your local machine.
