3 ms·
The biggest issue with this is when you deploy multiple applications to a server (e.g. 5 apps on IIS or whatever) and one of them kills off the box when it beha
by abrookewood 2y ago
The biggest issue with this is when you deploy multiple applications to a server (e.g. 5 apps on IIS or whatever) and one of them kills off the box when it behaves badly. You can auto-scale, but it takes time to provision new machines and until they are up, you are down. Once you've experienced this a few times, the desire to split out applications into micro-services gets pretty strong in order to limit the blast radius.
- cynicalsecurity 2y agoI'm sorry, what? IIS? o_O
- abrookewood 2y agoThe web server that many of us are stuck with unfortunately ;)
- ironhaven 2y agoAh there's your problem. Don't use IIS on Windows Server 2008!
- abrookewood 2y agoWe don't always get a choice.
- nitwit005 2y agoNo matter what auto-scaling solution you pick, it'll take time to start fresh new instances.
- abrookewood 2y agoAgreed, but if you are running on micro-services and an app crashes, you don't lose everything (hopefully). It's not enough to make me want to use micro-services everywhere, but it is a consideration. I'd like to see things work on Erlang/Elixir in Production and whether that works better, since the BEAM is very good at preventing individual processes from dominating the server and is also very good at recovering from errors.