4 ms·
If your services are already parallelizable to the degree that they could sit on separate VM's, couldn't you just run them side by side on the same machine with
by aston 19y ago
If your services are already parallelizable to the degree that they could sit on separate VM's, couldn't you just run them side by side on the same machine without all of the extra overhead a VM gives you? Maybe this is a Rails-related problem, but in general the hard part is not the move from parallelized tasks on one machine to many. The big problem is taking some non-parallel code and trying to distribute it much later on.
- wmf 19y agoIn this case we're really talking about configuration isolation. If you're running a database and a Web server on one machine and then want to move them onto separate machines, you have to untangle and move the config files. But if they're separate VMs from the start, then there's nothing to untangle.
- aston 19y agoAgain, the process of getting your services to the level that they can run independently (read: non-tangled config files) means that you don't need separate VM's.