Microservices with an API gateway

/02 About

Independently deployable services, each owning its data, behind an API gateway, with asynchronous events between them.

A system split by business capability into services that each own their data and release on their own schedule. One API gateway is the entry point for clients; services talk to each other through events where they can. When to use: several teams working on one product, parts that need to scale or release independently, and a domain with clear boundaries. Trade-offs: team autonomy and independent scaling, paid for with distributed data, eventual consistency, more moving parts and a real need for observability and automation. Start with a modular monolith if the boundaries are not yet clear.

Published by Lattix · 12 elements · 15 relationships · validated on publish