Microservices
In depthConcept
Architectural style that splits an application into small, independently deployable services.
Microservices, explained
Written by EduVerseWhat it is
Microservices is an architecture style where an application is built as a set of small services, each responsible for one part of the business, such as orders, payments or users. Each service runs as its own process, usually has its own database, and talks to the others over the network through APIs or messages.
Why teams use it
In a large organization, separate services let teams build, deploy and scale their part without waiting on everyone else. The price is high: network calls fail, data is spread across databases, and debugging means following one request through several services. For a small team, a well-structured monolith is usually the easier and cheaper start.
An example from work
A customer reports that checkout fails, but the checkout service’s logs look fine. You search your logging tool for the request’s trace id and find that the inventory service, two calls further down, timed out. In a monolith that would have been one stack trace; here you follow the request across services.
Our own explanation, not a quote from the book.
In the book
Sentences from The Software Realm, Decoded that mention Microservices, exactly as printed.
2 more passages about Microservices in the full book
Read every conversation where Microservices comes up, with the interactive slides and demos.
Where it fits
Scalable system components that teams can develop independently
Coverage in the book
Covered in depth: multiple pages with explanations, examples and simulations.
