Menu

1 / 2

Read/Write Controversy

DEV Community: redis·Bhanu partap·15 days ago
#xaxs4Tqk
#devtoredis#devto#dev#write#schema
Reading 0:00
15s threshold

Imagine you run a busy restaurant kitchen.

PostgreSQL -> chefs, waiters -> cache/Redis

The Write Side (Chefs) need things organized perfectly. Ingredients are in separate labeled containers.

Sauces here,

vegetables there,

meats in the fridge.

Everything has its own place so chefs can prep fast and never mix up orders.

This is your normalized Postgres schema. Clean, strict, no duplicates. Perfect for writing new orders.

OK:)

Now,

The Read Side (Waiters & Managers) need the opposite.

When a customer asks “Where is my order?”, the waiter does not want to check 7 different containers.

They want one single plate with everything ready to serve.

When the manager asks “How many biryanis did we sell yesterday?”, they do not want to open every container and count manually.

They want a pre-made summary sheet. This is your dashboard and reporting queries.

Right now your restaurant is using the same setup for both. Chefs are happy but waiters are running everywhere.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.