Resource-Oriented API DesignDesign APIs from domain behavior before choosing endpoint shapes.Available: Payment endpoint case study
REST · OpenAPIPlannedPublic curriculum
What comes after
the foundations.
Eighteen planned field guides connect API contracts and durable data to distributed systems and real-time delivery. A topic becomes a lesson only after it is complete and reviewed.
TopicSystem focusStatus
Stage 1 · API contracts and durable data
Durable Data and TransactionsReason from storage guarantees to application correctness.Available: Payment transaction case study
PostgreSQL · transactionsPlannedCaching as Controlled StalenessTreat every cache as an explicit staleness budget.
Redis · cachingPlannedDeferred Work and Job QueuesMove work off the request path without losing delivery semantics.Available: Reliable jobs case study
queues · workersPlannedSearch Beyond SQL LIKEUnderstand what a search engine stores before tuning relevance.
Elasticsearch · searchPlannedStage 2 · Reliability and service operations
Failure Semantics and ResilienceDesign the failure path before production designs it for you.Available: Retry and outage exercise
resilience · retriesPlannedService-to-Service ContractsChoose a protocol by coupling and delivery needs.
gRPC · microservicesPlannedConfiguration as a Runtime ContractMake invalid configuration fail before traffic arrives.
configuration · secretsPlannedObservability from Signals to DecisionsStart with debugging questions and derive the telemetry you need.Available: Request tracing case study
OpenTelemetry · loggingPlannedGraceful Lifecycle ManagementTreat process lifecycle as part of request correctness.
shutdown · KubernetesPlannedStage 3 · Security, scale, and delivery
Backend Security by Trust BoundarySecure transitions between trust zones instead of memorizing vulnerability names.
security · OWASPPlannedScaling the Request PathFind the bottleneck before adding machines.Available: Reproducible query measurement
scaling · performancePlannedScaling Data and StateScale state without losing the invariants that make it useful.
sharding · replicationPlannedConcurrency, Parallelism, and BackpressureMatch the execution model to the work and its capacity limit.
concurrency · event loopPlannedContainers and Delivery SystemsMake a release reproducible before making it frequent.
Docker · KubernetesPlannedTests as Executable BoundariesChoose tests by the boundary that can fail.Available: Executable failure tests
testing · contractsPlannedMessaging and Event StreamsSeparate message transport from the business guarantee you need.
Kafka · messagingPlannedReal-Time ConnectionsDesign the connection lifecycle, not only the happy-path message.
WebSockets · SSEPlanned