Microservices and APIs for public-sector platforms
Why microservice and API architectures are a way to evolve public platforms — not a fashion of smaller deployments.
A public-sector platform is rarely one application. It is a set of institutional processes, integrations and operational constraints that have to keep running while the software changes.
Microservices and APIs are useful here when they encode those boundaries: services that can be integrated, contracts that other systems can depend on, and deployments that can run in cloud or hybrid environments.
They are not useful when they fragment a system that still needs a single operational picture — availability, performance, audit.
The design work is therefore conservative: microservice architectures where the institution needs independent evolution; APIs where systems and agencies have to interconnect; technical coordination between development and infrastructure so the architecture can actually be deployed.
That is the difference between a diagram of services and a platform a public institution can operate.