Practical difference from Cloud Run

[Gabriel Axel]

Greetings. I watched the videos and read the docs of the new Cloud Run service and also took a look at the comparison table between GAE and Cloud Run, and to my understanding Cloud Run covers everything GAE Standard and Flexible do without any of their limitations. Maybe the only thing GAE "has over" Cloud Run is not having to write Dockerfile (except for Flexible custom runtime). Did I miss anything? Once Cloud Run goes GA, what use cases would be preferable for GAE over it?

[Nicolas Grilly]

On Wed, Apr 10, 2019 at 11:23 PM Gabriel Axel <guz...@gmail.com> wrote:

I watched the videos and read the docs of the new Cloud Run service and also took a look at the comparison table between GAE and Cloud Run, and to my understanding Cloud Run covers everything GAE Standard and Flexible do without any of their limitations. Maybe the only thing GAE "has over" Cloud Run is not having to write Dockerfile (except for Flexible custom runtime). Did I miss anything? Once Cloud Run goes GA, what use cases would be preferable for GAE over it?

I'm wondering the same. Can you share the link to the comparison table between Cloud Run and App Engine you mentioned?

[Gabriel Axel]

This is the comparison table between the different container running options: https://cloud.google.com/container-options/

On Thursday, April 11, 2019 at 4:26:55 AM UTC+3, Nicolas Grilly wrote:

On Wed, Apr 10, 2019 at 11:23 PM Gabriel Axel <guz...@gmail.com> wrote:

I watched the videos and read the docs of the new Cloud Run service and also took a look at the comparison table between GAE and Cloud Run, and to my understanding Cloud Run covers everything GAE Standard and Flexible do without any of their limitations. Maybe the only thing GAE "has over" Cloud Run is not having to write Dockerfile (except for Flexible custom runtime). Did I miss anything? Once Cloud Run goes GA, what use cases would be preferable for GAE over it?

I'm wondering the same. Can you share the link to the comparison table between Cloud Run and App Engine you mentioned?T

[Mike Liu]

Also interested in what networking differences there are. For example, can cloud run services reach compute instances on the same default project network?

We use cloud tasks to distribute/connect a lot of pipelines, doesn't seem to be listed as compatible w/ normal cloud run. (assuming everything is reachable via gke flavor)

https://cloud.google.com/run/docs/using-gcp-services

[Nicolas (Google Cloud Platform Support)]

Hi Gabriel,

Thanks for bringing those questions to our attention, I will forward them to the documentation team. 

Have a great day!

[Steren Giannini]

Hi Gabriel,

I am the product manager for Cloud Run, and worked on App Engine in the past.

As you noticed, the very first thing to take into consideration is that App Engine is a GA product, Cloud Run was just been announced and is in early Beta.

At a high level, choosing between App Engine and Cloud Run is mostly about the abstraction layer you want to use:

- Cloud Run only takes container images, while this gives you flexibility but this also requires you to work with containers.

- App Engine takes source code. The experience is tailored to the various supported languages, and when deployed, the language runtimes are automatically updated for you.

(- Cloud Functions takes function as source code and offers a quick development experience)

We are heavily investing into App Engine, for example, at Next 2019, we announced the availability of new second generation runtimes as well as  VPC access. We are committing to support our App Engine customers for the many years to come.

Today, App Engine has a lot of features that Cloud Run does not have: VPC access, Cloud SQL connectivity, the ability to do traffic migration or to serve static files.

I hope this helps.

We will publish more guidance in our official documentation.

Thanks for your message.

Steren 

[Barry Hunter]

Guess, depends on your point of view but one of the big things with App-engine (in particular 'Standard', flexible doesnt have quite as many!), is the Native APIs. 

From the table;

• Native support for microservices, authorization, SQL and NoSQL databases, logging, security scanning, and content delivery networks

Like https://cloud.google.com/appengine/docs/standard/python/datastore/  

Although of course that API has been 'genericized' and available outside of AppEngine

https://cloud.google.com/datastore/docs/concepts/overview 

so could be used in Cloud Run?

More

https://cloud.google.com/appengine/docs/standard/python/refdocs/

Some like

https://cloud.google.com/appengine/docs/standard/python/refdocs/google.appengine.api.images

I think are still relatively 'unique' and not outside of AppEngine (although of course other ways of doing the same things!)

On Wed, Apr 10, 2019 at 10:24 PM Gabriel Axel <guz...@gmail.com> wrote:

Greetings. I watched the videos and read the docs of the new Cloud Run service and also took a look at the comparison table between GAE and Cloud Run, and to my understanding Cloud Run covers everything GAE Standard and Flexible do without any of their limitations. Maybe the only thing GAE "has over" Cloud Run is not having to write Dockerfile (except for Flexible custom runtime). Did I miss anything? Once Cloud Run goes GA, what use cases would be preferable for GAE over it?

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/df3597aa-4854-4850-8568-e9c0e74902cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.