Microservices

Some of this article's listed sources may not be reliable. Please help improve this article by looking for better, more reliable sources. Unreliable citations may be challenged and removed. (October 2018) (Learn how and when to remove this message)

This section's tone or style may not reflect the encyclopedic tone used on Wikipedia. Relevant discussion may be found on the talk page. See Wikipedia's guide to writing better articles for suggestions. (June 2024) (Learn how and when to remove this message)

In software engineering, a microservice architecture is an architectural pattern that arranges an application as a collection of loosely coupled, fine-grained services, communicating through lightweight protocols. One of its goals is to enable teams to develop and deploy their services independently. This is achieved by reducing several dependencies in the codebase, allowing developers to evolve their services with limited restrictions, and hiding additional complexity from users.^[1] Consequently, organizations can develop software with rapid growth and scalability, as well as use off-the-shelf services more easily. Communication requirements are reduced. These benefits come with the cost of maintaining decoupling, so a microservice architecture may be suitable only if the application is too complex to manage as a monolith.^[2] Interfaces need to be designed carefully and treated as public API. One technique used is having multiple interfaces on the same service or multiple versions of the same service to avoid disrupting existing users of the code.

A microservice is analogous to Bounded Context in Domain Driven Design.^[3]