Thanks for the breakdown :)

On Wednesday, July 11, 2018 at 2:54:27 PM UTC+3, Ani Hatzis wrote:
>
> Maybe Cloud Functions will be added to Choosing a Computing Option 
> <https://cloud.google.com/docs/choosing-a-compute-option> once it gets 
> out of beta?
>
> In general I would say, that Cloud Functions (almost no control, focus on 
> code) is on the opposite side of Compute Engine (full control, lots of 
> DIY). Compared to App Engine, GCF is "even more serverless", probably more 
> suitable for small jobs, rather than fully fledged web apps / API backends. 
> GAE comes with different scalability options and version/traffic 
> management, and I believe that automated testing and deployment of an app 
> with dozens of endpoints, maybe hundreds, is easier with such features. 
> (Although Testing and CI/CD 
> <https://cloud.google.com/functions/docs/bestpractices/testing> is 
> possible with GCF).
>
> On the other hand, if you want to build just a few functions to accompany 
> Firebase, or utility functions for Cloud Storage, or integrate (GCP) 
> resources through Pub/Sub and light-weight computing, then GCF might be the 
> better option.
>
> With the rise of microservice architecture, GCF might become an excellent 
> compute option for microservices, too. However, it's still in beta, and I 
> believe that a few features are missing yet that would go a long way here: 
> Google-managed SSL with custom domains, builtin client authentication, and 
> better control of versions (or traffic migration). AFAIK, App Engine's Task 
> Queue API is promoted to a stand-alone product, Memcache, too. Add Storage 
> and Datastore to the mix and I see that GCF can become a reasonable 
> alternative to GAE in more use-cases.
>
> Of course, a rather different roadmap for GCF could be to somehow merge 
> GCF with its cousin from the Google apps family, Google Apps Script, but I 
> don't expect that to happen.
>
>
> On Wednesday, July 11, 2018 at 10:23:13 AM UTC+2, David Komer wrote:
>>
>> Just to bump this - the linked docs are great for comparing between App 
>> Engine Standard and Flexible, but it doesn't really address Cloud Functions.
>>
>> It would be helpful to have a comparison / best-practices guideline for 
>> choosing between Cloud Functions and App Engine
>>
>> On Saturday, 30 June 2018 21:30:19 UTC+3, George (Cloud Platform Support) 
>> wrote:
>>>
>>> If your intention is to deploy a full-fledged app, you have the choice 
>>> between the Standard Environment and Flexible. The "Choosing an App Engine 
>>> Environment" online document 
>>> <https://cloud.google.com/appengine/docs/the-appengine-environments> 
>>> should help you in taking the decision best suited to your needs. In both 
>>> cases, the managed environment works transparently in ensuring that your 
>>> desired functionality is there. You can configure your app specifying how 
>>> its services scale. Instances are created or stopped in response to 
>>> traffic. You may have a look at the "How Instances are Managed" page 
>>> <https://cloud.google.com/appengine/docs/standard/java/how-instances-are-managed>
>>>  
>>> for more information. 
>>>
>>> Cloud Endpoints is a distributed API management system, not suitable 
>>> for a priority job queue. 
>>>
>>

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@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/84f1d8d7-73eb-4f8a-9337-9aed9ba937c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to