Grokking Microservices for System Design Interviews

0% completed

​

Module Introduction

1. What This Module Covers

Splitting the services was the decision everyone saw. Splitting the data is the one that matters more.

The moment each service owns its own database, one sentence becomes true and stays true for the life of the system: no transaction can span two services.

A transaction is a group of writes that either all happen or none happen. Your database engine gives you that promise, but only for data it can see. An order and its payment now live in different databases. No single engine can see both, so no single engine can guarantee they change together.

.....

.....

.....

Like the course? Get enrolled and start learning!