Why apps split 'changing data' and 'reading data' into two completely separate lanes

Sat, 29 Aug 2026 00:14:56 +0900

🤔 What Is It?

CQRS(Command Query Responsibility Segregation)

CQRS is a rule for building apps that says: the part of the app that changes data (like posting a comment) must be completely separate from the part that reads data (like scrolling through comments). Keeping them apart means each side can be made super-fast at its one job.

🧩 Like a school library with two separate desks

Imagine your school library has two completely different desks on opposite sides of the room. At the REQUEST DESK you hand the librarian a slip saying ‘I’d like to borrow Harry Potter’ — the librarian fetches the book, stamps it, and updates the big official record book. That desk’s only job is to change things. On the other side is the SEARCH COMPUTER — you type in any title and it instantly shows you what’s available, who wrote it, how many pages it has. The search computer never stamps anything or moves a single book; its only job is to read and display. The search computer even has its own simplified copy of the information it needs, so it never has to wait around while the librarian is busy stamping books. These two desks are completely independent — and that’s exactly what CQRS does inside an app.

How Patroni Keeps Your Database Running Even When Servers Crash

Wed, 22 Jul 2026 07:22:28 +0900

🤔 What Is It?

Patroni 기반 분산 PostgreSQL, Patroni HA

Patroni is smart coach software that watches over a team of database servers — if the main server breaks, it instantly picks a backup to take over so your app never goes offline.

🧩 Like a soccer team with an automatic coach

Imagine a soccer team where one player is chosen as the captain — they call all the plays and everyone follows them. Three other players are backup captains who watch every single move the main captain makes and copy every strategy note into their own notebooks, second by second. A super-smart coach named Patroni watches everyone from the sideline, and the whole team shares one giant whiteboard called etcd that always shows exactly who the current captain is. If the main captain suddenly twists their ankle and can’t play, Patroni instantly checks the backups, picks the one whose notebook is most up-to-date, writes the new name on the whiteboard, and the game keeps going — all in a few seconds. Nobody in the stands even notices the switch happened.

Databases on Explain It

Why apps split 'changing data' and 'reading data' into two completely separate lanes

🤔 What Is It?

🧩 Like a school library with two separate desks

How Patroni Keeps Your Database Running Even When Servers Crash

🤔 What Is It?

🧩 Like a soccer team with an automatic coach