5 ms·

Do you know how Google Cloud Functions compares with AWS and Azure?

spyspy 9y ago
If you're going to be handling http requests it's almost a given you'll be using AppEngine rather than Cloud Functions. Still "serverless" but more tools and languages to choose from.
- the_common_man 9y ago
  AppEngine is more like a PaaS and not like 'serverless'
  - seangrogg 9y ago
    This. AppEngine assumes an "always on" mentality and is far from "pay for use" unless your "use" is 24/7.
    - octalmage 9y ago
      AppEngine standard can actually scale down to 0 instances when not in use to save money. Still very different from a serverless architecture though.
      - nothrabannosir 9y ago
        Not the flexible environment iirc. Which is basically the reasonable env to expect, now. Standard env has some aging issues that keep getting worse. most notably jvm 7, if that’s your poison, but just all round crippled env lacking standard libs and with lock in substitutions. As far as I remember, that is..
        iangudger 9y ago
        Java 8 is now supported with the full standard library: https://cloud.google.com/appengine/docs/standard/java/runtime-java8 https://cloud.google.com/appengine/docs/standard/java/runtim...
- dragonwriter 9y ago
  > If you're going to be handling http requests it's almost a given you'll be using AppEngine rather than Cloud Functions Why? Cloud Functions support HTTP. I mean, if you can stay within AppEngine’s free tier quotas, there's a clear reason to use it, but otherwise it would seem to be a matter of weighing pros and cons, with HTTP alone not deciding that you should use AE over CF.
- vira28 9y ago
  Are you kidding? You know how much you have to pay for AppEngine's right?!!
  - jpatokal 9y ago
    Nothing, if it's a small app? https://cloud.google.com/free/docs/always-free-usage-limits#gae_name https://cloud.google.com/free/docs/always-free-usage-limits#... Disclaimer: I work at GCP.
seangrogg 9y ago
GCF still suffers from JS lock-in, as they currently only support Node, thus you can't make a .NET comparison in the first place. That being said, of the various offers I really like the UI and the like. Disclaimer: I am at Google, but not on GCF.
- thesandlord 9y ago
  You technically can hack it to work: https://medium.com/@salmaan.rashid/running-net-on-google-cloud-functions-977e1a1c489 https://medium.com/@salmaan.rashid/running-net-on-google-clo... Native support for more languages is coming.

If you're going to be handling http requests it's almost a given you'll be using AppEngine rather than Cloud Functions. Still "serverless" but more tools and languages to choose from.

the_common_man 9y ago
AppEngine is more like a PaaS and not like 'serverless'
- seangrogg 9y ago
  This. AppEngine assumes an "always on" mentality and is far from "pay for use" unless your "use" is 24/7.
  - octalmage 9y ago
    AppEngine standard can actually scale down to 0 instances when not in use to save money. Still very different from a serverless architecture though.
    - nothrabannosir 9y ago
      Not the flexible environment iirc. Which is basically the reasonable env to expect, now. Standard env has some aging issues that keep getting worse. most notably jvm 7, if that’s your poison, but just all round crippled env lacking standard libs and with lock in substitutions. As far as I remember, that is..
      - iangudger 9y ago
        Java 8 is now supported with the full standard library: https://cloud.google.com/appengine/docs/standard/java/runtime-java8 https://cloud.google.com/appengine/docs/standard/java/runtim...
dragonwriter 9y ago
> If you're going to be handling http requests it's almost a given you'll be using AppEngine rather than Cloud Functions Why? Cloud Functions support HTTP. I mean, if you can stay within AppEngine’s free tier quotas, there's a clear reason to use it, but otherwise it would seem to be a matter of weighing pros and cons, with HTTP alone not deciding that you should use AE over CF.
vira28 9y ago
Are you kidding? You know how much you have to pay for AppEngine's right?!!
- jpatokal 9y ago
  Nothing, if it's a small app? https://cloud.google.com/free/docs/always-free-usage-limits#gae_name https://cloud.google.com/free/docs/always-free-usage-limits#... Disclaimer: I work at GCP.

seangrogg 9y ago

GCF still suffers from JS lock-in, as they currently only support Node, thus you can't make a .NET comparison in the first place. That being said, of the various offers I really like the UI and the like. Disclaimer: I am at Google, but not on GCF.

thesandlord 9y ago
You technically can hack it to work: https://medium.com/@salmaan.rashid/running-net-on-google-cloud-functions-977e1a1c489 https://medium.com/@salmaan.rashid/running-net-on-google-clo... Native support for more languages is coming.