Cilantrobyte.

Tech Stacks · Data

Redis

The cache, the queue, the session store, the rate limiter.

Category

Data

At the studio

Since 2019

Projects shipped

3 case studies

Status

Active

(01) Our take

Redis is the duct tape of modern web infrastructure. We use it as a cache in front of Postgres, as a job queue (via BullMQ), as a session store, and as a rate-limiting primitive. It's one of a small number of technologies we install by default on almost every project that has backend infrastructure at all.

We're cautious about using Redis as a primary store. Its persistence guarantees are weaker than Postgres, and we've seen teams build themselves into corners by treating it as a database. For ephemeral state and derived data, it's excellent.

(02) What we build with it

Typical work

  • Caching layer in front of Postgres
  • Background job queues (BullMQ, SidekiQ)
  • Session storage for authenticated apps
  • Rate limiting and abuse prevention

(03) How we engage

Engagement shape

Never the headline technology — always part of a larger backend stack.

(04) In production

Where we've shipped it

All case studies →

(05) Pairs with

Works well with

Technologies we reach for alongside Redis in most engagements.

Data

PostgreSQL

The default database. For almost everything.

Backend

Node.js

The default backend runtime for JavaScript shops.

Infra

AWS

The default cloud when compliance, scale, or sovereignty demand it.

Infra

Docker

The container standard, still.

Thinking about a Redis project?

Start a project →back to all stacks