# System design and delivery — Learning path | Yishto

Canonical page: https://yishto.com/en/learn/delivery/

Author: [Yishto](https://yishto.com/en/about/)

Understand deployment and scaling tradeoffs and verify recovery.

Deliver and recover a system with clear boundaries.

## System design and delivery

- [Design failure and recovery before splitting services](https://yishto.com/en/learn/delivery/distributed-systems-and-recovery/index.md): 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](https://yishto.com/en/learn/delivery/containers-orchestration-and-iac/index.md): 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](https://yishto.com/en/learn/delivery/deployment-dns-gateways-and-cdn/index.md): 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](https://yishto.com/en/learn/delivery/cicd-monitoring-and-incidents/index.md): 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](https://yishto.com/en/learn/delivery/security-boundaries-and-threat-models/index.md): Map a document assistant’s assets, authorization, and execution boundaries to check cross-user access, model injection, dependency code, and exposure through logs.