Agent WranglersINF-61Recommended
Choose the hosting model from written needs
Write down what the service needs before you choose between a managed platform, serverless functions, containers on a platform or your own servers. Pick the model that meets every need, and record why.
How to do it
List the longest request or job, the peak and idle traffic, the memory per request and any open connections such as websockets. Add background jobs, where the data must live, the monthly budget and who will patch servers. Serverless functions suit short requests that come in bursts. AWS Lambda, for example, stops any call after 15 minutes. Long jobs, steady load and open connections suit containers or servers. Your own servers make you responsible for updates, as Install security updates by themselves says. Keep the choice as a decision record, as Keep decision records with a status describes. Apps made in an AI app builder have their own signs, listed in Know when to move off the builder.
How to check
A decision record names the hosting model and lists each need with a number. It is newer than the last change of hosting model.
Sources
Related rules
- Install security updates by themselves in Infrastructure
- Keep decision records with a status in Engineering
- Know when to move off the builder in AI development
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/hosting-model">Agent Wranglers infrastructure playbook</a>. In code you write, add a comment next to it with the same link.