Module 2: Microservices & Service Decomposition
This page aggregates the generated reference routes used by the learner-facing module.
- Semester:
semester-08-system-design-leadership - App:
production
Read only if stuck
- Fundamentals of Software Architecture: Monolithic vs Distributed Architectures
- Fundamentals of Software Architecture: Architecture Styles
- Fundamentals of Software Architecture: Modularity
- Fundamentals of Software Architecture: Component-Based Thinking
- System Design Primer: Application Layer, Microservices, and Service Discovery
- Fundamentals of Software Architecture: Have Business Domain Knowledge
- Fundamentals of Software Architecture: Discovering Components
- Fundamentals of Software Architecture: Connascence
- Fundamentals of Software Architecture: Analyzing Trade-offs
- System Design Primer: RPC and REST
- System Design Primer: Asynchronism
- System Design Primer: Database federation and sharding
- System Design Primer: RDBMS and Replication
- Fundamentals of Software Architecture: Communication
- Fundamentals of Software Architecture: Database Partitioning
- Fundamentals of Software Architecture: Unit and Functional Testing Checklist
- Fundamentals of Software Architecture: Fitness Functions
- System Design Primer: Communication HTTP
- System Design Primer: Communication TCP/UDP
- System Design Primer: Load Balancer
- System Design Primer: Reverse Proxy
- System Design Primer: Availability Patterns
- Fundamentals of Software Architecture: Event-Driven Architecture Style
- Fundamentals of Software Architecture: Request-Reply
- Fundamentals of Software Architecture: Asynchronous Capabilities
- Fundamentals of Software Architecture: Preventing Data Loss
- Fundamentals of Software Architecture: Operations / DevOps
- Fundamentals of Software Architecture: Engineering Practices
- Fundamentals of Software Architecture: Measuring Architecture Characteristics
- Fundamentals of Software Architecture: Making Teams Effective
- Fundamentals of Software Architecture: Team Warning Signs
- Fundamentals of Software Architecture: Integrating with the Development Team
- Fundamentals of Software Architecture: The Software Architect as a Leader
- system-design-primer: Application Layer
- FoSA: Monolithic vs Distributed
- FoSA: Modularity
- FoSA: Component-Based Thinking
- FoSA: Discovering Components
- FoSA: Connascence
- system-design-primer: Federation/sharding
- system-design-primer: RPC and REST
- system-design-primer: Asynchronism
- FoSA: Fitness Functions
- FoSA: Event-Driven Style
- FoSA: Request-Reply
- system-design-primer: Availability Patterns
- FoSA: Measuring Architecture Characteristics
- FoSA: Engineering Practices
- FoSA: Making Teams Effective
Optional deep dive
- System Design Primer: Real-World Architectures
- Fundamentals of Software Architecture: Architecture Decisions
- Fundamentals of Software Architecture: Architecture Decision Records
- Fundamentals of Software Architecture: Risk Matrix
- Fundamentals of Software Architecture: Choosing the Appropriate Architecture Style
- Fundamentals of Software Architecture: Diagramming and Presenting Architecture