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.
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.
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.
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/
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