AWS Lambda vs Cloud Functions for Firebase vs Google Cloud Functions

Need advice about which tool to choose?Ask the StackShare community!

AWS Lambda

20.2K
15.2K
+ 1
427
Cloud Functions for Firebase

444
367
+ 1
6
Google Cloud Functions

442
432
+ 1
20
Advice on AWS Lambda, Cloud Functions for Firebase, and Google Cloud Functions

Need advice on what platform, systems and tools to use.

Evaluating whether to start a new digital business for which we will need to build a website that handles all traffic. Website only right now. May add smartphone apps later. No desktop app will ever be added. Website to serve various countries and languages. B2B and B2C type customers. Need to handle heavy traffic, be low cost, and scale well.

We are open to either build it on AWS or on Microsoft Azure.

Apologies if I'm leaving out some info. My first post. :) Thanks in advance!

See more
Replies (2)
Anis Zehani

I recommend this : -Spring reactive for back end : the fact it's reactive (async) it consumes half of the resources that a sync platform needs (so less CPU -> less money). -Angular : Web Front end ; it's gives you the possibility to use PWA which is a cheap replacement for a mobile app (but more less popular). -Docker images. -Kubernetes to orchestrate all the containers. -I Use Jenkins / blueocean, ansible for my CI/CD (with Github of course) -AWS of course : u can run a K8S cluster there, make it multi AZ (availability zones) to be highly available, use a load balancer and an auto scaler and ur good to go. -You can store data by taking any managed DB or u can deploy ur own (cheap but risky).

You pay less money, but u need some technical 2 - 3 guys to make that done.

Good luck

See more

My advice will be Front end: React Backend: Language: Java, Kotlin. Database: SQL: Postgres, MySQL, Aurora NOSQL: Mongo db. Caching: Redis. Public : Spring Webflux for async public facing operation. Admin api: Spring boot, Hibrernate, Rest API. Build Container image. Kuberenetes: AWS EKS, AWS ECS, Google GKE. Use Jenkins for CI/CD pipeline. Buddy works is good for AWS. Static content: Host on AWS S3 bucket, Use Cloudfront or Cloudflare as CDN.

Serverless Solution: Api gateway Lambda, Serveless Aurora (SQL). AWS S3 bucket.

See more
Decisions about AWS Lambda, Cloud Functions for Firebase, and Google Cloud Functions
Clifford Crerar
Software Engineer at Bidvest Advisory Services · | 9 upvotes · 51.1K views

Run cloud service containers instead of cloud-native services

  • Running containers means that your microservices are not "cooked" into a cloud provider's architecture.
  • Moving from one cloud to the next means that you simply spin up new instances of your containers in the new cloud using that cloud's container service.
  • Start redirecting your traffic to the new resources.
  • Turn off the containers in the cloud you migrated from.
See more

When adding a new feature to Checkly rearchitecting some older piece, I tend to pick Heroku for rolling it out. But not always, because sometimes I pick AWS Lambda . The short story:

  • Developer Experience trumps everything.
  • AWS Lambda is cheap. Up to a limit though. This impact not only your wallet.
  • If you need geographic spread, AWS is lonely at the top.
The setup

Recently, I was doing a brainstorm at a startup here in Berlin on the future of their infrastructure. They were ready to move on from their initial, almost 100% Ec2 + Chef based setup. Everything was on the table. But we crossed out a lot quite quickly:

  • Pure, uncut, self hosted Kubernetes — way too much complexity
  • Managed Kubernetes in various flavors — still too much complexity
  • Zeit — Maybe, but no Docker support
  • Elastic Beanstalk — Maybe, bit old but does the job
  • Heroku
  • Lambda

It became clear a mix of PaaS and FaaS was the way to go. What a surprise! That is exactly what I use for Checkly! But when do you pick which model?

I chopped that question up into the following categories:

  • Developer Experience / DX 🤓
  • Ops Experience / OX 🐂 (?)
  • Cost 💵
  • Lock in 🔐

Read the full post linked below for all details

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of AWS Lambda
Pros of Cloud Functions for Firebase
Pros of Google Cloud Functions
  • 128
    No infrastructure
  • 82
    Cheap
  • 69
    Quick
  • 58
    Stateless
  • 47
    No deploy, no server, great sleep
  • 11
    AWS Lambda went down taking many sites with it
  • 6
    Event Driven Governance
  • 6
    Easy to deploy
  • 6
    Extensive API
  • 6
    Auto scale and cost effective
  • 5
    VPC Support
  • 3
    Integrated with various AWS services
  • 4
    Up and running
  • 1
    Multi-region
  • 1
    Affordable
  • 6
    Serverless Applications
  • 4
    Its not AWS
  • 3
    Simplicity
  • 2
    Free Tiers and Trainging
  • 1
    Built-in Webhook trigger
  • 1
    Customer Support
  • 1
    Simple config with GitLab CI/CD
  • 1
    Typescript Support
  • 1
    Blaze, pay as you go

Sign up to add or upvote prosMake informed product decisions

Cons of AWS Lambda
Cons of Cloud Functions for Firebase
Cons of Google Cloud Functions
  • 6
    Cant execute ruby or go
  • 1
    Compute time limited
  • 0
    Can't execute PHP w/o significant effort
    Be the first to leave a con
    • 1
      Node.js only
    • 0
      Typescript Support
    • 0
      Blaze, pay as you go

    Sign up to add or upvote consMake informed product decisions

    What is AWS Lambda?

    AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.

    What is Cloud Functions for Firebase?

    Cloud Functions for Firebase lets you create functions that are triggered by Firebase products, such as changes to data in the Realtime Database, uploads to Cloud Storage, new user sign ups via Authentication, and conversion events in Analytics.

    What is Google Cloud Functions?

    Construct applications from bite-sized business logic billed to the nearest 100 milliseconds, only while your code is running

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention AWS Lambda, Cloud Functions for Firebase, and Google Cloud Functions as a desired skillset
    What companies use AWS Lambda?
    What companies use Cloud Functions for Firebase?
    What companies use Google Cloud Functions?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with AWS Lambda?
    What tools integrate with Cloud Functions for Firebase?
    What tools integrate with Google Cloud Functions?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    GitHubPythonNode.js+47
    53
    70598
    GitHubDockerAmazon EC2+23
    12
    6407
    JavaScriptGitHubPython+42
    52
    20506
    What are some alternatives to AWS Lambda, Cloud Functions for Firebase, and Google Cloud Functions?
    Serverless
    Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.
    Azure Functions
    Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.
    AWS Elastic Beanstalk
    Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring.
    AWS Step Functions
    AWS Step Functions makes it easy to coordinate the components of distributed applications and microservices using visual workflows. Building applications from individual components that each perform a discrete function lets you scale and change applications quickly.
    Google App Engine
    Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.
    See all alternatives