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.
App Engine runs your Java web application using a Java 6
JVM in a safe "sandboxed" environemnt. App Engine invokes
your app's servlet classes to handle requests and prepare
responses in this environment.
Sounds like their answer for Java8 is probably the same for Python3:
"To echo comment #66, App Engine in fact is not going away. To the contrary, we're investing heavily, and the new hosting environment that is based on containerized virtual machines (what we're currently calling "App Engine Managed VMs") allows you to utilize Java 8 as well as Servlet 3.x."
I work in Product Management on App Engine, and I'd like to assure you that we're continuing to invest in the product. We already support Java 8 in beta on Managed VMs (https://cloud.google.com/appengine/docs/managed-vms/), and the same is true for Python 3. Once Managed VMs goes GA, we expect that most of our customers will find that it provides all the benefits of App Engine with increased flexibility around the programming language, native code, etc.
well if you just use appengine without using a vendor lock-in service, i.e. using cloudsql instead of datastore, etc. than you probably won't run into trouble.
but it looks like appengine still has it's momentum (they actually added java8 support lately)
After more than 8 years of coding in Java, I had to pick up Python (and Django) so as to start using GAE for my startup.
Now, looking at those sample code in Java (and JSP) and the related XML configurations for GAE, I don't think I want to go back to Java - unless I am paid to do so, say for services.
I'm a Product Manager on App Engine and I truly apologize for the trouble you went through when you tried the platform. We have kicked off a large initiative to update and enhance our docs, and we just recently launched our new App Engine docs, an ongoing project of course. You can check them out here:
Please give the new set of docs a try and please give us feedback when you see errors or generally when the content is not up to par with what you expect. There is a tool on the top right hand side of every page that explains this.
Additionally, it's pretty quick to get an application up and running on GAE as well. Not entirely trivial at the moment, but it's getting close (still waiting on the release of a couple gems before i can say that's the case).
Google recently released a Java runtime environment for their App Engine platform. As a software development organization, this offering is of special interest to Nagarro
Can you give some examples of how that is the case? I don't know of any App Engine Services available on Java not available on Python (or vice-versa). They seem to be equally supported.
We've used almost all libraries with no issues. The only problematic ones are those that try to implement networking code on their own. Appengine has some limitations on the type of networking calls you can do but most libraries support delegating that work. The new Java 8 runtime has A LOT of these restrictions removed.
There is very little appengine specific code in our app with the exception of our data layer. Because we use AppEngine datastore (the only option at the time), we are pretty tied to it. I feel like migrating cloud platforms is always a large undertaking and appengine would be no different. If we were starting today, we'd probably consider using Cloud SQL or Spanner, but the good thing now is that you have a choice.
Aside from the autoscaling, the idea of never thinking about machines is really nice. We never think about OS's, patches, networking, etc.
The other nice benefit is the deployment story. You can organize your application into services, deploy them individually, traffic split between version, rollback quickly, setup staging, etc. Its very well implemented and the fact that we never think about it is really nice.
Try out Google App Engine's Java support and the Eclipse plug-in, and if you're after a Java framework check out GWT.
I love Python and work in it almost entirely now, but previously worked with Java (yes I know the joke about them being the same with the whitespace re-arranged).
GAE gets rid of most of the configuration and scaling pain. Plus it's free to get started. There are some limitations, but essentially it makes deploying Java web apps a snap.
reply