Analyze Code in Multiple Repositories
The core idea behind microservices is to structure your system as a set of loosely coupled services, which—ideally—are independently deployable and execute in their own environment. Different services exchange information via a set of well-defined protocols, and the communication mechanism can be both synchronous, as in a blocking request-response, or asynchronous.
So far, this all sounds like a fairly technical view, but microservices also promise an architectural style that supports autonomous teams that can work independently on different services. Of course, such team independence isn’t really a property of microservices themselves, but rather a result of any well-designed system oriented around use ...
Get Software Design X-Rays now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
