Chapter 6. Conclusion
Microservice Architecture is an architectural style that provides a number of benefits by adopting a divide and conquer approach to software design and deployment. Microservices can be individually maintained, isolated, scaled up or down, or upgraded and replaced. The modularity of microservices can affect both the requirements and the benefits of the deployment. The best solution is not universal and entirely depends on the client environment and application requirements. After providing a thorough discussion on microservices and some of the factors that go into determining a client’s needs and cost to benefit parameters, this reference architecture focuses on business-driven microservices that are not directly exposed to the outside world. An aggregation layer provides a simple and familiar interface to clients, while taking advantage of most benefits provided by this architectural style.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.