4 ms·

I think it's actually good as soon as you're doing microservices and don't want to use any managed vendor lock in service like app engine. The setup is easy if

I think it's actually good as soon as you're doing microservices and don't want to use any managed vendor lock in service like app engine. The setup is easy if you use a managed kubernetes offering and it provides so many things out of the box you'd otherwise have to take care of yourself. Service discovery, service lifecycles, updates, storage management, logs, load balancing (inter-service), all those things you should automate even if you have 5 servers, and k8s makes this darn easy in my opinion. The declarative abstraction is also very easy to use and intuitive in my opinion.

nickbauman 8y ago
I routinely take app engine apps and run them on the FOSS AppScale platform unchanged. For the things you can't port, like using Google as your auth, there are 3rd party solutions for that already. Choosing Google's App Engine is more than just choosing a managed solution, too. You choose it because of Google's reach: consider, for a moment, how you send a push notification to an Android device. When you do it from Google's cloud, your metal is co-located with their push infra. Also caching, logging, tracing and even a global CDN is integrated into the platform. Think of the cost of having to sort this yourself.