[ I had my first network interruption on my VPS in years this weekend... so just a touch nervous and looking at other options ]
[ I had my first network interruption on my VPS in years this weekend... so just a touch nervous and looking at other options ]
I found that if you were even a bit off the beaten path they didn’t do much more than reboot and check if the disks had filled up.
In that awkward in-between phase of starting to grow and not quite there yet for another set of back-end hands :)
- Realtime kernel/lib patching.
- Patch management.
- 24x7 monitoring and response.
- Metric collections, alerting, and health reviews.
- Tuning and infrastructure best practices wherever you are (AWS/GCP/Azure/mnx/colo).
- Ad-hoc support - example this week -- one customer who runs large ecommerce valentine day related -- needed eyes on all infrastructure. We sat in slack with them, and huddled realtime to work through any issues.I can certainly see in future when we're a bit bigger it might be interesting and having a lot more infrastructure to manage - but right now when we've barely (infact only once in past year had an issue) then not quite justifiable.
Like I say, it's that awful middle ground of "can't really justify it, but also would like to be able to switch off!" I'll reach out to stay in touch for future.