Watch a 49-minute conference talk exploring how dark energy and dark matter serve as powerful metaphors for understanding microservices architecture patterns. Learn how competing forces in software development mirror cosmic phenomena, with dark energy representing repulsive forces that drive service separation and dark matter illustrating efficient interactions between services. Delve into critical architectural decisions including monolithic versus microservices approaches, orchestration versus choreography tradeoffs, and strategies for managing team size and cognitive load. Discover practical insights on platform teams, frontend development with Federated GraphQL, and prioritizing critical operations. Through this astronomical lens, gain a deeper understanding of how to balance conflicting forces in microservices design while minimizing both runtime and design-time coupling between services.
Dark Energy and Dark Matter as Metaphors for Microservices Design Patterns
Overview
Syllabus
Introduction
Overview
Patterns
Design Process
Dark Energy Dark Matter
Dark Energy repulsive forces
Dark Matter efficient interactions
Dark Matter minimize runtime coupling
Dark Matter minimize design time coupling
Colocating tightly coupled subdomains
Balancing conflicting forces
Monolithic Architecture
Operations
Monolith Architecture
Accept Ticket
Delivery Management
Design Decisions
Microservices vs monolithic architecture
Orchestration vs choreography
Team size
Microservices
Cognitive Load
Platform Teams
Frontend
Federated GraphQL
Most Critical Operations First
Final Thoughts
Outro
Taught by
InfoQ
