Redis Streams on S2

You can now access streams on S2 Cloud directly via Redis clients. The integration is in beta and available to all S2 users.

Check out the docs to get started right away.

Why Redis?

We’re building S2 to make streams a serverless cloud storage primitive.

The Redis Streams interface brings that model to clients that many people already use.

It supports a subset of Redis Streams commands relevant to append-only workloads, mapping commands such as XADD, XREAD, and XRANGE into S2 operations.

Who is this for?

Many of our customers found S2 after running into limitations working with append-only streams of data, like LLM tokens, telemetry, and notifications.

They often come from Redis, where they’ve had to trim streams or set an aggressive TTL to stay within their instance’s memory limits.

They might be delivering live output via Redis, but then need a second system to keep that data available for reads days or months later.

Plus, Redis is typically expensive to run in a fully durable setup.

Our take on Redis Streams with S2 is pretty unique:

• Streams can grow infinitely. Stream size isn’t limited by memory, so the same stream used for real-time outputs can be your long-term storage. Even the number of streams is unlimited.
• All writes are fully durable before acknowledgement. Streams provide cross-zone durability and strong read-your-writes consistency.
• It's actually serverless. The Redis interface uses S2’s core pricing, based on operations, traffic, and storage duration. You only pay for what you use.

For workloads with long retention, Redis Streams on S2 can be an order of magnitude more cost-effective than other Redis solutions.

What’s the catch?

We support only a subset of Redis Streams commands. At least for now, that means: no consumer groups, no acks/nacks, no deleting individual messages.

Durable storage comes with a latency tradeoff too: writes are acknowledged in the low tens of milliseconds. Pipelined appends let you keep multiple writes in flight and sustain throughput.

If you need a high-throughput, fully durable, append-only stream with infinite retention, I don’t think you can do better than S2. That’s our whole thing! Now we can offer it directly to Redis clients.