I don't have a company, but I do host a few play projects. My advise is mostly around using cloud providers.. 1) build for limited/easy observational/maintenan

I don't have a company, but I do host a few play projects. My advise is mostly around using cloud providers.. 1) build for limited/easy observational/maintenance. Adding observers and maintaining systems is time you could spend elsewhere. 2) favor self-healing. I generally do this by using severless services -- code won't suddenly execute differently in a new lambda/function or container, so if the data center has an issue, my issue is resolved when there's is. 3) keep your running stack simple. The less services you leverage, the less you are impacted by issues. It may make more sense to use the database for locking instead of redis because that's one less thing to learn. 4) reproducibility of your environment. DNS is almost the only thing I need to set up manually (because the effort to automate making SOA/NS links). But after that, I can rebuild my entire code stacks and make a new dev environment in minutes. I then can load up the recent DB backup. Having this also makes it easier to deploy in multiple regions, if you get to that level of redundancy needed. I guess my advise is mostly keep it simple so your less likely to have an issue.