Skip to main content

Learning Resources

This generated surface maps a learner-facing curriculum unit to its canonical source routes.

Curriculum surface

  • Open learner-facing unit
  • Curriculum path: content/curriculum/production/semester-08-system-design-leadership/module-02-microservices-service-decomposition/resources.md
  • App: production
  • Semester: semester-08-system-design-leadership
  • Module: module-02-microservices-service-decomposition
  • Unit kind: resource
  • Curation level: module_curated

Learning objectives

  • Explain Learning Resources as a boundary and coordination problem, not a default move toward more services.
  • Use Learning Resources to reason about coupling, ownership, deployment cost, and operational complexity in a real organization.
  • Use fundamentals-of-software-architecture, system-design-primer to connect the learner page to decomposition strategies, data ownership, and service collaboration tradeoffs.

Prerequisites

  • Comfort with structured system-design thinking and the cost of architectural boundaries from module 01.

Source books

  • fundamentals-of-software-architecture
  • system-design-primer

Source routes

Fundamentals Of Software Architecture

  • /books/fundamentals-of-software-architecture via FoSA: ADRs, FoSA: Analyzing Trade-offs, FoSA: Architect as Leader, FoSA: Architecture Decisions, FoSA: Architecture Styles, FoSA: Armchair Architect, FoSA: Async Capabilities, FoSA: Case Study -- Going Going Gone, FoSA: Case Study -- Silicon Sandwiches, FoSA: Case Study — Going Going Gone, FoSA: Case Study — Silicon Sandwiches, FoSA: Characteristics Ratings, FoSA: Checklists, FoSA: Choosing Appropriate Style, FoSA: Communication, FoSA: Component-Based Thinking, FoSA: Connascence, FoSA: Database Partitioning, FoSA: Discovering Components, FoSA: Engineering Practices, FoSA: Event-Driven Style, FoSA: Fitness Functions, FoSA: Have Business Domain Knowledge, FoSA: Integrating with Dev Team, FoSA: Leading by Example, FoSA: Making Teams Effective, FoSA: Measuring Characteristics, FoSA: Measuring Modularity, FoSA: Measuring Modularity 1+2, FoSA: Mediator Topology, FoSA: Modularity, FoSA: Monolithic vs Distributed, FoSA: Negotiation, FoSA: Operations/DevOps, FoSA: Preventing Data Loss, FoSA: Request-Reply, FoSA: Reuse and Coupling, FoSA: Silicon Sandwiches Partitioning, FoSA: Team Warning Signs, FoSA: Testing Checklist

System Design Primer

  • /books/system-design-primer via primer: Application Layer, primer: Application Layer (disadvantages), primer: Application Layer disadvantages, primer: Asynchronism, primer: Availability Patterns, primer: CAP Theorem, primer: CDN, primer: Consistency Patterns, primer: DNS, primer: Database Federation, primer: HTTP, primer: Latency vs Throughput, primer: Load Balancer, primer: Performance vs Scalability, primer: RDBMS Replication, primer: RPC and REST, primer: RPC/REST, primer: Reverse Proxy, primer: SQL or NoSQL, primer: Security, primer: TCP/UDP

Supporting curriculum routes

No supporting curriculum routes linked yet.

External enrichment

AI companion modes

  • Explain simply
  • Diagnose my confusion
  • Revision mode
  • Connect forward / backward

Source-of-truth note

This teaching unit is learner-facing guidance assembled from multiple canonical book routes. Use the listed source books as the primary conceptual spine for Learning Resources, and treat outside material as supporting enrichment only.