Fault Isolation
In a monolithic application, a memory leak in one component, or even a third-party library, can affect the entire application and be hard to track down.
One of the benefits of a microservices architecture is the isolation of components or features. If one service crashes, it’s quite possible the rest of the application can continue to operate until that service recovers. This of course assumes the service is implemented to handle the faults. Also, if one service is suffering from growing memory pressure due to a leak, it can be much easier to identify the service causing the issue. We might still be able to handle requests for the application even though one of its services is down. As depicted in Figure 1.4, even though one service ...
Get Microservices with Docker on Microsoft Azure™ (includes Content Update Program) 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.
