Stateless API with a managed database, one server
Ex-PaaS teams often land here: the API is already stateless and the database already managed, but the whole thing runs on one box with no load balancer in front. One prerequisite, then the standard path.
- Prerequisite work
- LB only
- Time to set up
- 1 h
- Adapter
- Snapshot or webhook
- Fit
- 7/10
Prerequisites, time and fit are the ADR-0028 row for this case. Hetscale's own setup is about 15 minutes in every case; the rest is work on your side.
Steps
- 01Add a Hetzner load balancer
Create one with a health check on the API’s health endpoint, terminate TLS there, point DNS at it, and put the server behind it.
- 02Connect read-only
The 14-day Observe trial reads the last 30 days of metrics for the server behind the load balancer and ranges what a group would have done.
- 03Choose snapshot or webhook
Snapshot the server as the template, or let your pipeline deploy to each node Hetscale announces.
- 04Rehearse, then go Live with minimum 2
One Rehearsal, then the range the report suggests.
FAQ for this case
Is a stateless API a good fit?
Yes: no local state, a health endpoint, an external database. The only missing piece is the load balancer, which is why the fit is 7 and the time one hour.