Editing Microservices Architecture (section)

== <span style="color: #FFFFFF;">Understanding</span> ==
Microservices are understood through '''Independence''' and '''Communication'''.

'''1. Decentralized Everything''':
In a Monolith, there is one giant database.
* In Microservices, every service has its **own database**.
* If the "Reviews" database crashes, people can still "Buy" items.
* If the "Shipping" team wants to use a new programming language (like Rust) while the "Web" team uses Javascript, they can!

'''2. Talking through APIs''':
Since the services are separate, they must talk over the network (usually using JSON or gRPC).
* This creates "Latency" (a delay), but it also creates "Safety."
* You can "Mock" a service—meaning you can test the "Payment" app by pretending the "Bank" app is working, even if it's not finished yet.

'''3. The "Pizza Team" Rule''':
Jeff Bezos famously said that a team should be small enough to be fed by "Two Pizzas."
* Each pizza team "Owns" one microservice.
* They build it, they test it, they run it, and they "Wake up at 3 AM" if it breaks.
* This creates a sense of "Ownership" that is impossible in a giant 1,000-person project.

'''Conway's Law''': The observation that the structure of a piece of software will eventually look exactly like the structure of the organization that built it. If you have 5 teams, you will eventually have 5 microservices.
</div>

<div style="background-color: #8B0000; color: #FFFFFF; padding: 20px; border-radius: 8px; margin-bottom: 15px;">