News for hackers. Stuff that matters.

A comment on Moving from Heroku to Google Kubernetes Engine. Parent comment

Re:Moving from Heroku to Google Kubernetes Engine by alasdair_ on Thursday April 04, 2019 @10:06PM (#19579020)
>I'm interested to know why they didn't move to Google AppEngine instead, which offers a better experience and more advanced features overall. Especially considering that AppEngine is a direct competitor to Heroku than Kubernetes engine.

AppEngine has an enormous number of limitations that you only hit once you scale up and gets very expensive very quickly.

[ Parent | on HN ]
Re:Moving from Heroku to Google Kubernetes Engine by latchkey on Thursday April 04, 2019 @11:22PM (#19579392)
It really bugs me when people make extremely blanket statements like this.

This is a huge success story that I was part of: https://cloud.google.com/customers/gearlaunch/

At our peak, we were processing $500,000 of online orders per day and spending about $5k/month on our entire GPC bill. It was a rounding error compared with our income.

The biggest expenditure was actually on the Postgres database servers that we needed for our analytics, not on AppEngine.

[ Parent | on HN ]
Re:Moving from Heroku to Google Kubernetes Engine by neya on Thursday April 04, 2019 @10:33PM (#19579151)
> AppEngine has an enormous number of limitations

I have used AppEngine in production for about 50+ clients and I am genuinely really curious to know what these limitations are. Maybe it is dependent on the programming language/framework? I run Phoenix/Elixir with Vue.JS + PostgreSQL as standard for most of my clients, it's really a breeze to work with.

In addition, these are the advantages of working with AppEngine:

https://news.ycombinator.com/item?id=17516530

[ Parent | on HN ]
Re:Moving from Heroku to Google Kubernetes Engine by clhodapp on Thursday April 04, 2019 @11:32PM (#19579441)
The AppEngine Standard Java 8 API is severely limited because it is coupled to the Servlet API, which severely screwed up on the design of its async API. As a Scala developer, this limitation pretty much sinks the platform for me, since the flexible environment is really expensive and has a worse value proposition vs managed Kubernetes.
[ Parent | on HN ]
Re:Moving from Heroku to Google Kubernetes Engine by haimez on Friday April 05, 2019 @12:55AM (#19579829)
App engine flex is a “bring your own container” set up.
[ Parent | on HN ]
Re:Moving from Heroku to Google Kubernetes Engine by clhodapp on Friday April 05, 2019 @02:36AM (#19580239)
Right, but at that point, you almost might as well move up to "full" Kubernetes if you know it. I'm not saying that there's no use case for App Engine flex, just that it is kind an uncomfortable middle-ground between standard and k8s.
[ Parent | on HN ]
Re:Moving from Heroku to Google Kubernetes Engine by devlance on Monday April 15, 2019 @04:21PM (#19668559)
Worth pointing out that Cloud Run was just released and maybe better meets your needs? https://cloud.google.com/run/
[ Parent | on HN ]
Re:Moving from Heroku to Google Kubernetes Engine by rlancer on Thursday April 04, 2019 @10:13PM (#19579048)
Is standard more expensive in reality? Any data on this, flex is certainly very expensive
[ Parent | on HN ]
Re:Moving from Heroku to Google Kubernetes Engine by haimez on Friday April 05, 2019 @01:01AM (#19579854)
Flex is not at all very expensive. Per instance cost is about 1/2 the cost compared to heroku, putting it on par with the likes of ECS in terms of cost but ships with usable monitoring, logging, and metrics out of the box with extremely generous free tiers that stay free way longer and that are still marginally cheaper than what you’d pay in AWS land if you exceed them.
[ Parent | on HN ]