Agent WranglersINF-67Recommended
Keep an exit plan for each platform
Keep a written plan to move the service to another host within 5 working days. List each feature only this platform offers, with the replacement for each.
How to do it
Treat the database, storage, queues and mail as attached services. Then moving one changes settings, not code, as the twelve-factor app describes. Platform-only features, such as special queues, edge functions or key-value stores, are the parts that tie you down. Wrap each behind one module of your own. Define the setup in code, as Define every resource in code says. Keep backups off the platform, as Back up off the machine says. Try the move during the game day in Plan for losing a provider.
How to check
The exit plan lists every platform-only feature with a replacement. At the last game day, the service started on a second host from the code and a backup, and passed its smoke tests.
Sources
Related rules
- Define every resource in code in Infrastructure
- Back up off the machine in Operations
- Plan for losing a provider in Operations
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/infrastructure/hosting-platforms/platform-exit-plan">Agent Wranglers infrastructure playbook</a>. In code you write, add a comment next to it with the same link.