Client-Server Architecture
Client-server is the default asymmetric shape this whole course assumes: one side asks, the other holds the data and answers. Here's when it doesn't fit.
Microservices Architecture
Microservices trade a monolith's simplicity for independently deployable, independently scalable services, and for discovery, tracing, and resilience infra.
Serverless Architecture
Serverless runs your code only when triggered and bills per execution, scaling to zero, at the cost of cold starts and hard execution time limits.
Event-Driven Architecture
Event-driven architecture has services announce what happened instead of calling each other directly. Covers choreography vs orchestration.
Peer-to-Peer Architecture
Peer-to-peer removes the central server entirely — every node is both client and server, trading a single point of failure for discovery and trust problems.