Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by hehheh on Friday August 05, 2016 @06:36PM
(#12236158)
Those aren't really alternatives to GAE IMO unless you would also say that a laptop is an alternative. A real GAE alternative would be a hosted solution that doesn't require you to install an OS or even know what OS it's using.
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by scrollaway on Friday August 05, 2016 @06:51PM
(#12236220)
Such alternatives would have the same massive downsides as GAE (outdated software by design, lock-in by design).
I'm not saying "Don't use GAE because it's expensive/google/whatever". I'm saying "Don't use GAE or anything like it".
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by NetStrikeForce on Friday August 05, 2016 @09:25PM
(#12236626)
I think both AWS and Azure have pretty strong PaaS services where you just deploy your [nodejs|python|php] app. Heroku also comes to mind...
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by jacques_chester on Saturday August 06, 2016 @09:49AM
(#12238101)
AWS has Elastic Beanstalk. Azure is still finding their own PaaS pathway.
Cloud Foundry gives you the "just push" experience for both of these (as well as vSphere, OpenStack, GCP and more to come). It's open source, with the IP owned by an independent foundation.
Disclosure: I work for Pivotal, we donate the majority of engineering on Cloud Foundry.
Within Google, either of the GCEs (https://cloud.google.com/compute/ https://cloud.google.com/container-engine/) depending on your architecture.