Module 5

Application Layer

How to split and run the code itself: monoliths and microservices, finding services, making retries safe and keeping servers stateless.

0% read

Your progress is saved in this browser. Nothing is sent to us.

Module 05

0 / 4 read

5.1 Read
Monolith vs Microservices
A monolith ships the whole application as one unit; microservices split it into small services that deploy on their own. Learn what each costs, when splitting pays off, and how to split along business boundaries.
Intermediate 7 min
5.2 Read
Service Discovery
Service instances start, stop and move all the time, so callers cannot hard-code addresses. Learn how a service registry, health checks and client-side or server-side discovery let services find each other.
Intermediate 6 min
5.3 Read
Idempotent Operations
Networks lose responses, so clients retry, and a retried payment must not charge twice. Learn what idempotency means, which HTTP methods have it, and how idempotency keys make any operation safe to retry.
Intermediate 7 min
5.4 Read
Stateless Services and Sessions
A stateless server keeps nothing about a user between requests, so any server can handle any request. Learn where session data goes instead: a shared store, a database or a signed token.
Beginner 6 min