Product-Oriented Architecture: A Company Scaling Strategy or an Architectural Illusion?
summary
Examines Product-Oriented Architecture as a way to scale a company from one solution to an ecosystem of 10+ independent products over three years. Covers setting autonomy boundaries between products, designing integration interactions, applying reuse and isolation principles to avoid architectural chaos, and building cross-product business processes; aimed at architects, CTOs and technical leaders.
AI-written summary · about
chapters (14)
- 0:00Developer to architect
- 1:06Product ecosystem context
- 6:48Scaling 500 microservices
- 10:00POA pillars
- 11:24Per-product architecture
- 15:35Standards and practices
- 17:46API Gateway types
- 21:40Webhooks vs Kafka
- 23:47Monitoring tools
- 26:16Infrastructure layers
- 28:00Pros and cons
- 30:52When to adopt
- 33:44Feature vs product mindset
- 35:11Q&A
related talks
30mBlending Product Thinking with Architecture
47mBlending Product Thinking with Architecture
51mScaling the Product Mindset: From Individual Ideas to Team Culture
24mThe too many faces of Architecture
47mArchitecture and Corporate Operating Structure: a Cloud Puzzle
23mScaling engineering teams with an architecture North Star
39mTeam Topologies, Software Architecture & Complexity
53mKeynote - Software Architecture, Team Topologies and Complexity Science