Skip to content
AITroveRead. Build. Understand.

DevOps projects

Apply delivery and recovery decisions in a disposable service environment.

Work through a complete release and recovery exercise with a disposable ledger service. Preserve evidence of the artifact, traffic check, rollback, and restored data.

Project

Prepare first

Service-path diagnosis

Release boundary hardening

Resilience game day

Production boundaries exercise

Stateful recovery exercise

Cross-system release exercise

Failure-boundary drill

Failover and release safety exercise

Host and protocol failure drill

Cloud boundary recovery drill

Cluster control recovery drill

Artifact trust recovery drill

Data continuity recovery drill

Observability pipeline failure drill

Service traffic contract drill

Terraform ownership handoff drill

Network path diagnosis drill

CI evidence integrity drill

Storage lifecycle recovery drill

Configuration delivery recovery drill

Runtime isolation drill

Cost and capacity recovery drill

Object archive recovery drill

Cloud authorization and audit drill

Supply evidence promotion drill

Fenced recovery execution drill

GitOps operating-boundary drill

TLS trust rotation drill

Platform self-service drill

Memory failure drill

Serverless boundary drill

Headless publishing release drill

Browser and edge security release drill

Delivery measurement ledger drill

Kafka stream recovery drill

RabbitMQ delivery recovery drill

Redis recovery boundaries drill

systemd service fault drill

Linux host change drill

Linux storage fault drill

Curriculum

Produce evidence from build through restore.

  1. 1Project: release and recover a ledger API
  2. 2Project: diagnose a broken service path
  3. 3Project: harden a release boundary
  4. 4Project: run a service resilience game day
  5. 5Project: reconcile production boundaries
  6. 6Project: stage and recover a stateful release
  7. 7Project: release across identity, capacity, DNS, and events
  8. 8Project: drill replica lag, replay, and incident control
  9. 9Project: protect a release through failover and capacity pressure
  10. 10Project: recover a host and protocol failure chain
  11. 11Project: recover a saturated cloud boundary
  12. 12Project: recover a degraded cluster control plane
  13. 13Project: recover an artifact trust chain
  14. 14Project: recover a database change stream and restore boundary
  15. 15Project: recover an observability pipeline without hiding user impact
  16. 16Project: release a service through connection and cache failures
  17. 17Project: hand off Terraform-managed infrastructure without a replacement surprise
  18. 18Project: diagnose a failing network path from client to backend
  19. 19Project: prove a receipt release passed the checks that matter
  20. 20Project: keep receipt data through Kubernetes storage transitions
  21. 21Project: prove configuration and identity delivery during a release
  22. 22Project: harden a document worker without losing its recovery path
  23. 23Project: lower platform cost without losing recovery capacity
  24. 24Project: recover a versioned object archive
  25. 25Project: prove a cloud deployment's authority and audit trail
  26. 26Project: promote an image with verifiable supply-chain evidence
  27. 27Project: rehearse a fenced regional recovery and failback
  28. 28Project: test GitOps render, ownership, prune, and rollback boundaries
  29. 29Project: rotate service trust and contain an exposed TLS key
  30. 30Project: prove a self-service platform request end to end
  31. 31Project: diagnose a memory failure without moving it to another Pod
  32. 32Project: prove a serverless release survives duplicate events and rollback
  33. 33Project: publish, unpublish, and recover a headless learning site
  34. 34Project: release browser and edge controls without breaking publishing
  35. 35Project: build an auditable delivery and recovery measurement ledger
  36. 36Kafka stream recovery project: broker fault, replay, and state rebuild
  37. 37RabbitMQ delivery recovery project: confirms, quorum, and queue cutover
  38. 38Redis recovery boundaries project: persistence, failover, resharding, and replay
  39. 39systemd service fault drill: readiness, restart, timer, and socket recovery
  40. 40Linux host change drill: reboot, access, firewall, and disk recovery
  41. 41Linux storage fault drill: space, mount, repair, RAID, and latency
Storage details