When you think of microservices, you probably think of centralized shared services. But there's another valid pattern that is rarely discussed

This article discusses a rarely discussed microservices pattern where the same microservice codebase is deployed inside multiple platforms rather than using a centralized shared service. It contrasts this with the traditional centralized model, tracing its roots from SOA to modern microservices. The author highlights downsides of centralization in cell-based architectures, such as cross-cell dependencies and shared failure domains, and proposes deploying the same service locally within each platform to achieve reuse without forced centralization. Caveats include strong ownership and selecting well-scoped, stateless capabilities like currency conversion.