How Composable Architectures can solve the reasons for Microservices
summary
Shows how adopting the Composable Enterprise framework overcomes microservice coupling by enforcing product-aligned boundaries, explicit API contracts and event streams, and moving crosscutting concerns into a platform. Concrete moves include creating platform teams and enabling teams, standardizing tracing/logging, and outsourcing TLS/SSL certificate management, backups, IAM and VPC concerns to the platform. After several projects over recent years this reduces direct integrations, improves developer velocity and joy, and makes deployments and upgrades less risky and more predictable.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 3:47Traditional IT systems challenges
- 13:06Business alignment in software
- 18:49Composable enterprise concept
- 26:47Building business components
- 32:29Platform teams and developer joy
- 37:30How to start improving
related talks
46mWhy Cross-Functional Teams Build Better Microservices
24mAgility through Composable Architecture
38mMicroservices Architecture’s Influence on Team Organization
52mWhat Does a Good Microservice Architecture Look Like?
24mPatterns of Evolution from Monolith to Microservices
49mMicroservices: An unexpected Journey
23mMicroservices Architectures: Agility vs Complexity
26mPros/Cons of Microservices