4 ms·
I've used App Engine a decent amount the past 8 years and I would say it's great for prototyping and quickly creating CRUD tools or simple services. But stop th
by blixt 10y ago
I've used App Engine a decent amount the past 8 years and I would say it's great for prototyping and quickly creating CRUD tools or simple services. But stop there, don't build a whole API that powers your app / service on top of App Engine. Having done exactly that, I feel that App Engine is being treated more and more like the unwanted step-child.
The more "adult" Cloud services are taking priority which is noticeable in the monitoring solutions and deploy tooling. I've seen bugs that you wouldn't expect in a production class service linger for months, requiring you to spend time working around them. And the CPU cost overhead of their heavily abstracted runtime is not dismissible if you compare running Docker instances in Kubernetes (Google Container Engine).
I really enjoy using GCP, the APIs and tools are much nicer than say AWS, and Google's offering has quickly caught up with competitors. I've just moved over to Docker instances which is ultimately cheaper, faster to deploy, more predictable, and more configurable.