> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/m/microservices.md). # Microservices An architectural style that structures an application as a collection of loosely coupled, independently deployable services. An architectural style that structures an application as a collection of services that are highly maintainable and testable, loosely coupled, independently deployable, and organized around business capabilities. Each microservice runs in its own process, owns its data, and communicates with other services through well-defined APIs -- typically REST or gRPC. Teams can develop, test, deploy, and scale individual services independently, using different programming languages and data stores as appropriate for each service's requirements. Microservices architectures rely heavily on API gateways. The gateway serves as a single entry point for clients, routing requests to the appropriate microservice and aggregating responses when a client request requires data from multiple services. Without a gateway, clients would need to know the location and interface of each individual service, creating tight coupling. The gateway also provides cross-cutting concerns like authentication, rate limiting, and logging that apply uniformly across all services, avoiding duplication of this logic in each microservice. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/m/microservices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.