Re:Auto-Scaling and Self-Defensive Services in Golang
by brianwawok on Sunday March 27, 2016 @10:23AM
(#11370031)
My thought as well. If your server is sized to handle 4 workers, run 4 workers.
If you want to autoscale to save costs cool. But then use a server only sized to hold 1 worker. Then the techniques in this post wont quite work.
The failure detector piece is neat, but if doing a true multi server scaling setup, may be better to just kill a hung VM and fire up a new one. Just as likely to be a server problem as a code problem. If automated why not just nuke it all.
For those of you who are experienced in platforms where this is a common practice, can you tell me why this is done? I have seen this done a lot.
Why don't people just launch more worker goroutines (or whatever their platform's concurrency primitives are) and max out their machine from a single process? Is it to keep the code simpler (i.e., it is easier to just spin up duplicate processes on the same machine) and not have to deal with any concurrency?