本文由 AI 分析生成
建立時間： 2026-03-28 來源： https://www.infoq.com/articles/navigating-microservices-architecture/
Summary
Asanka Abeysinghe’s 2016 InfoQ overview of microservice architecture (MSA) design considerations, covering inner architecture (service implementation) vs. outer architecture (platform capabilities), and the transition from SOA. Key advice: don’t throw away SOA — use middleware/ESB as a migration bridge.
Asanka Abeysinghe 2016 年 InfoQ 關於微服務架構（MSA）設計考量的概述，涵蓋內部架構（服務實現）與外部架構（平台能力），以及從 SOA 的過渡。關鍵建議：不要拋棄 SOA——使用中間件/ESB 作為遷移橋梁。
Key Points
- Inner architecture: service implementation — single purpose, single responsibility; self-contained deployment unit; API-first with Swagger; infrastructure choices (containers)
- Outer architecture: platform capabilities — connectivity, flexibility, scalability; API gateway, service mesh, analytics
- SOA transition: biggest mistake is throwing away SOA entirely; instead, use ESB/middleware as mediation layer to bridge legacy and new microservices
- Six inner architecture requirements: single purpose, technology choice freedom, API-first, containerized deployment, analytics/monitoring, polyglot but governed
- Context (2016): Gartner predicted 20% of large orgs would deploy microservices by 2017
Insights
This article is from 2016 at the height of microservices hype — its value now is historical context for understanding what the architecture looked like before Kubernetes became the de-facto deployment platform and before service mesh concepts matured. The ESB-as-bridge advice reflects enterprise reality: most large organizations have decades of SOA investments that can’t be replaced overnight. The inner/outer architecture distinction is useful vocabulary that remains relevant. The “polyglot but governed” tension is still live — teams want language freedom but need consistency for operations.
Connections
Raw Excerpt
The biggest mistake enterprises often make when implementing an MSA is to completely throw away established SOA approaches. The smarter approach is to consider an MSA as a layered system that includes ESB-like functionality to handle integration-related functions.