All topicsTopic 03 / 24
Intermediate 1 minute
Microservices Architecture
Microservices split a product into independently deployable services, each responsible for a focused business capability. Services communicate over a network and may own their data. This can let teams release and scale parts separately, but it adds operational work: service discovery, observability, retries, network failures, and contracts between teams.
Key idea
Microservices trade local simplicity for independent ownership and deployment.
See it in one picture
Follow the arrowsUsers
Identity
Catalog
Orders
Payments
Each service owns one job
Real-world example
A marketplace could separate identity, catalog, orders, payments, and notifications. A catalog team can scale search without deploying payment code, while both teams must handle network calls and versioned APIs.
Quick check