3 ms·
This has been a long time coming. The autoscaler has been an interesting, and possible the most interesting, part of AppEngine and IMHO has recently reached the
by mmastrac 12y ago
This has been a long time coming. The autoscaler has been an interesting, and possible the most interesting, part of AppEngine and IMHO has recently reached the point (in the last year-and-a-half) where I'd say I'd want to rely on it for production.
It wasn't always this way -- at one point we were having so many issues with AppEngine's autoscaling that we ended up in a meeting across from Ben Traynor and heard some of their engineers discussing post-mortems of scaling failures in gruesome detail. They've come a long way since then and AppEngine has really found its way from something of an internal science experiment to what I think is the best competitor for AWS' offerings.
FWIW, the "backend" or "basic" scaling module that was available for both AppEngine and GCE was so poor and unreliable that it made it nearly impossible to scale anything in a way other than manual. I honestly hope they deprecate this and roll the few features into the autoscaler.
- erjiang 12y agoI'm confused - are you saying that scaling was horribly broken for App Engine, not just Compute Engine? Because it seems that it's much simpler to scale App Engine apps and App Engine has been around a long time.
- mmastrac 12y agoAutoscaling was initially available for AppEngine only and the same (or similar) infrastructure is being made available to Compute Engine. Compute Engine had access to "basic scaling" which was so horribly broken and unreliable that you may as well just set up a static number of instances. The entire scaling infrastructure of AppEngine was horribly broken and unreliable up until a year-and-half or so ago, but they've put a lot of work into fixing that recently and it's in awesome shape now.