For example, a Server's:
- disk fails (ZFS with hot spares)
- power supply fails (each server has two)
- someone cut the power (there's another server)
---
Most issues will be caused by me, so the general answer is don't leave before testing.
- disk fails (ZFS with hot spares)
- power supply fails (each server has two)
- someone cut the power (there's another server)
---
Most issues will be caused by me, so the general answer is don't leave before testing.
I'm not a solo founder, but if I would be I would most likely pick a solution where I would have to maintain the least amount of infrastructure (e.g. using SAAS/FAAS offerings). That would mean in most cases someone else gets paged if things break. Still doesn't guarantee 100% availability since it can't prevent code bugs from doing bad things, but there would be still less things to worry about.