Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Yeah, but going from 1 to N instances is a big jump in complexity for not much more uptime.

I'd rather have a host that can do around three nines and just accept that as my upper bound.



view as:

The key moment is not to have any persistent state in the app. App may use a database, that's ok, but the app itself should not store any persistent state on a hard drive.

Once that simple requirement is met, the scaling becomes easy.


Right, but keeping a database externally adds a lot of complexity.

My apps are self-contained in a single Docker container. Just Go, SQLite, and Litestream:

https://mtlynch.io/litestream/


Legal | privacy