Hosting platforms

Required

• Test the service against every platform limit

  INF-62

  Keep a file of each platform limit the service can hit, with its value, plan and date from the provider's documents. Test the slowest request, the largest body and the peak memory against those limits before launch.

• Keep production data and secrets out of previews

  INF-64

  Give preview deployments their own secrets and a database with made-up data. A preview build never sees a production key or connection string, and its address asks visitors to sign in.

• Own the domain and DNS in your own accounts

  INF-68

  Register the domain and host its DNS in accounts the business owns. Keep them apart from the hosting platform and from any agency or contractor.

Recommended

• Choose the hosting model from written needs

  INF-61

  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.

• Choose regions from users and data rules

  INF-65

  Run the app and its database in the same region, chosen from where users are and where personal data may be stored. Pin that region on every resource, including logs and backups.

• Price data transfer and per-request charges before launch

  INF-66

  Before launch, estimate the monthly bill at 1, 10 and 100 times the expected traffic. Include data sent out, each request, each function call and each build, not only servers.

• Keep an exit plan for each platform

  INF-67

  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.