Synchronous REST/gRPC vs Asynchronous Events
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/concepts/cluster-04-service-communication/10-synchronous-rest-grpc-vs-asynchronous-events-primary.md - App:
production - Semester:
semester-08-system-design-leadership - Module:
module-02-microservices-service-decomposition - Unit kind:
concept - Curation level:
module_curated
Learning objectives
- Explain Synchronous REST/gRPC vs Asynchronous Events as a boundary and coordination problem, not a default move toward more services.
- Use Synchronous REST/gRPC vs Asynchronous Events to reason about coupling, ownership, deployment cost, and operational complexity in a real organization.
- Use
fundamentals-of-software-architecture,system-design-primerto 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-architecturesystem-design-primer
Source routes
Fundamentals Of Software Architecture
- /books/fundamentals-of-software-architecture via
FoSA: Asynchronous Capabilities,FoSA: Communication,FoSA: Event-Driven Architecture Style,FoSA: Mediator Topology,FoSA: Preventing Data Loss,FoSA: Request-Reply
System Design Primer
- /books/system-design-primer via
Primer: Asynchronism,Primer: Communication HTTP,Primer: Communication TCP/UDP,Primer: Consistency Patterns,Primer: RPC and REST
Supporting curriculum routes
No supporting curriculum routes linked yet.
External enrichment
- Martin Fowler: Microservices (
read_if_stuck) - Keeps the learner anchored in real tradeoffs when discussing service boundaries and organizational cost. - microservices.io: Service Decomposition (
official_docs_companion) - Adds concrete decomposition patterns that make service-boundary decisions more actionable.
AI companion modes
- Explain simply
- Socratic tutor
- Challenge my understanding
- Diagnose my confusion
- 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 Synchronous REST/gRPC vs Asynchronous Events, and treat outside material as supporting enrichment only.