System design and delivery
Understand deployment and scaling tradeoffs and verify recovery.
Deliver and recover a system with clear boundaries.
Chapters
Design failure and recovery before splitting services
Follow an order and inventory case through timeouts, idempotency, compensation, consensus, and restoration to verify the failure states introduced by service boundaries.
Trace responsibility from containers to clusters
Use a stateless preview API to distinguish images, instances, probes, scheduling resources, and infrastructure state, then check ownership across container and cluster delivery.
Put a service behind the right domain
Trace document-site delivery through domains, certificates, proxies, origins, and caches, including language variation, private responses, and the boundaries of hosting products.
Make every release verifiable and recoverable
Connect artifact tracking, required checks, user health, telemetry, and incident response through a search release, while separating code rollback from data recovery.
Design security boundaries from assets and entry points
Map a document assistant’s assets, authorization, and execution boundaries to check cross-user access, model injection, dependency code, and exposure through logs.