Uptime best practices for a service you run yourself
The habits that keep a small service reliable, from graceful shutdown to timeouts to knowing before your users do, and where Voroa helps you right now.
What this covers
Most downtime on a small service comes from a handful of avoidable habits rather than from infrastructure failing. Handle the shutdown signal so in-flight requests finish instead of being cut off mid-deploy. Put a timeout on every outbound call, because a dependency that hangs will otherwise tie up your service until it stops answering anyone. Keep state out of the process, so a restart costs nothing. Deploy small changes often, so when something breaks the list of suspects is short. And check your service from outside, since a service can be perfectly healthy from the inside and unreachable from the internet.
An uptime guide specific to Voroa is not published in the docs today. The practices above apply anywhere.