Working with Redis?

Redis out of memory or stuck on an old version? We fix it.

Redis is quick until it isn't. One day it is serving millions of requests a second, the next it is refusing writes because maxmemory filled, or a replica went read-only, or nobody is sure whether to stay on Redis or move to Valkey after the licence change. We work out what is actually happening and fix that.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

redis-server.log

still failing

What it is

Redis at a glance

Redis, short for Remote Dictionary Server, was created by Salvatore Sanfilippo in 2009. It began as an in-memory key-value store and grew into a richly-typed data store and messaging system used for caches, session stores, rate limiting, queues and real-time counters.

Redis was BSD-licensed until March 2024, when Redis Ltd. moved the source to RSALv2 and SSPL, which are no longer OSI-approved open source. The Linux Foundation then forked Redis 7.2.4 as Valkey, now backed by AWS, Google Cloud, Oracle and Ericsson. Redis Open Source is still available under the new licences for most self-hosting use cases.

Type
In-memory data store, cache and message broker
First released
2009
License
RSALv2 or SSPL for Redis 7.4 and later, BSD-3 for the Valkey fork
Maintained by
Redis Ltd. for Redis, the Linux Foundation for Valkey
Typically used for
Session stores, caches, rate limiting, queues, pub/sub, real-time counters, leaderboards

The honest version

Redis pros and cons

No technology is all upside. This is where Redis earns its place and where it tends to cause trouble.

Where Redis is strong

  • Extremely fast in-memory storeEverything lives in RAM, so reads and writes land in microseconds. A single modest node can serve well over a hundred thousand operations a second.
  • Rich data structuresStrings, hashes, lists, sets, sorted sets, streams, bitmaps, HyperLogLog and geo are all first class. Problems that would be awkward in a plain cache fit naturally in Redis.
  • Pub/sub and scriptingBuilt-in publish and subscribe channels and Lua scripting let you push messages and run atomic multi-step logic without a separate broker.
  • Replication, Sentinel and ClusterPrimary and replica replication is built in. Sentinel handles automatic failover and Cluster shards the keyspace across many nodes for horizontal scale.
  • Pipelining and transactionsClients can pipeline commands and wrap several writes in MULTI/EXEC blocks, which keeps throughput high over normal network links.
  • Small operational footprintOne small binary, one config file, and modest CPU needs for the work it does. It is unusually cheap to run for the throughput it delivers.

Where Redis bites

  • Licence changed in March 2024Redis moved from the BSD licence to RSALv2 and SSPL, which are not OSI-approved open source. The Valkey fork from the Linux Foundation is now the BSD successor and is what AWS, Azure, Google and Oracle ship.
  • Persistence has trade-offs teams missRDB snapshots are point-in-time and can lose the last few minutes of writes. AOF logs every write but grows until it rewrites. Running neither means a restart is an empty cache.
  • Memory is the hard limitIf used memory climbs past the maxmemory setting, writes fail with OOM until the eviction policy frees space. Choosing between noeviction, allkeys-lru, volatile-ttl and friends changes application behaviour in ways people forget.
  • Cluster mode breaks assumptionsMulti-key commands only work within a single slot, clients have to follow MOVED and ASK redirects, and Lua scripts have to pin their keys. Code written for a single Redis often needs careful work before it runs on a cluster.
  • Inherited caches rot quietlyOlder Redis instances accumulate keys with no TTL, debugging dumps, abandoned queues and session data from users who left years ago. Memory fills and nobody knows which keys are safe to remove.

Sound familiar?

Common Redis problems we fix

The Redis problems that bring people to us, and what you have once each one is fixed.

OOM command not allowed

Writes started failing with OOM

Used memory crossed the maxmemory line and the eviction policy either cannot free space or is set to noeviction. Raising the limit without picking a policy only delays the next outage.

Sized correctly, eviction tuned

licence changed to RSALv2 / SSPL

Unsure whether to stay on Redis or move to Valkey

The March 2024 licence change made Redis non-OSI open source. Valkey is the Linux Foundation fork and is now the default in the big clouds, but drop-in compatibility has limits.

A documented decision either way

MISCONF unable to persist on disk

Persistence silently stopped working

RDB save failing on a full disk or a read-only mount, or AOF rewrite stuck. Redis refuses writes until the operator either fixes the disk or disables stop-writes-on-bgsave-error.

Writes flowing, disk watched

READONLY · replica

The app is writing to a replica by accident

After a failover the roles swapped and the client kept talking to the same address. Sentinel or a proxy is meant to prevent this, but only if clients honour it.

Clients follow the primary

MOVED 5798 · slot not on this node

Cluster mode is confusing the application

The client library does not follow MOVED and ASK redirects, or code uses multi-key commands across slots. Works on single-node Redis, breaks under Cluster.

Cluster-aware client, hash tags where needed

slowlog: SMEMBERS 820ms

One command is blocking everything else

Redis is single-threaded for commands. A SMEMBERS on a million-member set, a KEYS on production or a big Lua script stalls every other client for the duration.

Slow commands replaced, cursor scans in place

last backup: unknown

The cache has become a database

Over time, data that only lives in Redis quietly becomes the only copy. A node reboot wipes it, and nobody has a current RDB or AOF to restore from.

Backups in place, source of truth clear

admin login: unknown

The previous team left the Redis to us

Nobody has the credentials, nothing is monitored, and the config was last edited years ago. We take it over, document it and put alerts on the parts that actually matter.

Owned, monitored, documented

What we do

Redis help, from rescue to upkeep

Call us for one OOM, or hand us the whole fleet.

Rescue
Out of memory, refusing writes, failing over badly. We get it serving again, then find out why it broke.
Memory and performance
Right-sizing maxmemory, picking an eviction policy that fits the workload, finding the keys and commands that are actually heavy.
HA and clustering
Sentinel set up and tested, Cluster designed with real slot planning, failovers rehearsed before anyone needs them.
Valkey migrations
Honest advice on whether to stay on Redis or move to Valkey, and a tested migration path when it is time.
Persistence and backups
RDB and AOF settings chosen deliberately, off-server copies, and restores that have actually been run.
Managed Tech
Memory and keyspace watched week to week, eviction policy reviewed as workloads change, failover drills run on a schedule, and someone to ring when a primary goes read-only.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Redis alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Redis questions

Something else? Call+1 737 727 7327

Should we migrate from Redis to Valkey after the licence change?

It depends on how you use Redis and who hosts it. For teams on AWS ElastiCache, Google Memorystore or Azure Cache, the managed services are moving to Valkey anyway, so you inherit it. For self-hosters who need true open source, Valkey is now the BSD-licensed successor and is a reasonable default. Teams using Redis Stack modules or Redis Enterprise usually stay on Redis.

Why does our Redis server hit OOM errors?

The used memory has crossed the maxmemory setting and the eviction policy either cannot free enough space or is set to noeviction. The fix is rarely just a bigger server. We work out which keys are using the memory, whether TTLs are missing, and which eviction policy matches how the application actually reads and writes.

Can you set up Redis Sentinel or Cluster properly?

Yes. We design the topology for your workload, configure quorum and failover timeouts that make sense, test failover before it is needed, and make sure the client libraries actually follow MOVED and ASK redirects or the Sentinel primary address.

Why are our Redis caches full of stale data?

Usually a mix of keys written without a TTL, abandoned queues from old features, and session data from users who never came back. We audit what is in the keyspace, add TTLs where they belong, and set an eviction policy so memory does not silently fill again.

Can you take over Redis infrastructure from a previous team?

Yes. We pick up undocumented Redis fleets, work out what each instance is used for, document the config and failure modes, and put monitoring in place for the things that actually cause outages.

How much does Redis help cost?

Estimates are free. Send over INFO output and the slowlog, and we quote a plan before anyone touches the server.

Free estimate

Redis giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.