A great in-between is to simply have a backup server ready to go in a few minutes time. Super simple compared to orchestrated container system.
Of course for client projects that spec out a certain number of 9's must be done just so, but can also be billed accordingly.
It does seem to be an example of a "standard" architecture done well. Our application has a tiny fraction of the traffic and it struggles with some things.
Here's a series of blog posts with a lot more detail by one of their devs: https://nickcraver.com/blog/archive/
They're very optimized and can serve all of their traffic on a single webserver, redis instance and SQL server.
The nice side effect is they did migrate to .NET Core
And as another commenter said, another side effect was they got fault tolerant infrastructure. So not every minute they spent on migrating to "spot" instances is dedicated to that.
we basically only run jobs on the spot instances that don't need to run instantenious, so it's really cheap for us.
We have done the same - our bills went down, but not by as much as 80% I think closer to 50%. But it took a fair bit of developer time, and we now have a lot of Kubernetes related problems to deal with. I guess those will smooth out over time, but I don't think anyone ever factors in this stuff when they claim great savings. Developer time ain't cheap.
On a plus note, running multiple small boxes via Kubernetes does give you a more high availability system. If one instance goes down, there will still be another one available, so it's not all negative.