Need advice about which tool to choose?Ask the StackShare community!
AWS Lambda vs FaaS: What are the differences?
Key differences between AWS Lambda and FaaS
AWS Lambda and FaaS (Function as a Service) are both cloud computing services that allow developers to deploy and run code without the need to provision or manage servers. However, there are some key differences between the two:
Function boundaries: In AWS Lambda, functions are typically limited to a single programming language, such as Node.js, Java, or Python. On the other hand, FaaS platforms like OpenFaaS or Knative allow developers to run functions written in multiple languages within a single platform, providing more flexibility and choice.
Vendor lock-in: AWS Lambda is an Amazon Web Services (AWS) specific service, meaning that it ties developers to the AWS ecosystem. Alternatively, FaaS platforms are generally more open and can be deployed on various cloud providers, reducing vendor lock-in and enabling multi-cloud strategies.
Customization and control: With AWS Lambda, developers have limited control over the underlying infrastructure and are constrained by the service's limitations. On the other hand, FaaS platforms provide more customization options and control, allowing developers to fine-tune their functions and infrastructure to meet specific requirements.
Pricing model: AWS Lambda adopts a pay-per-use pricing model, charging for the total number of invocations and the execution duration of functions. In contrast, FaaS platforms may offer different pricing models, such as flat-rate or usage-based, giving developers more flexibility in terms of cost optimization.
Community and ecosystem: AWS Lambda is backed by a robust and extensive community of users, which results in a wide range of resources, documentation, and support available. FaaS platforms, while less established, are rapidly growing and have an active community, but may have fewer resources and support options compared to AWS Lambda.
Security and compliance: AWS Lambda is built on top of the AWS infrastructure, which is compliant with various industry standards and regulations, such as HIPAA or GDPR. FaaS platforms may have different security and compliance measures in place, depending on the cloud provider or deployment environment chosen.
In summary, AWS Lambda and FaaS differ in terms of function boundaries, vendor lock-in, customization, pricing model, community and ecosystem, as well as security and compliance measures.
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!
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
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.
Netlfiy Functions uses AWS Lambda under the hood, but Netlify adds some nice sugar. The biggest advantage is the local development experience with netlify-cli. This allows you to run your functions locally with local configuration or pull configs from the Netlify dashboard. I built a health-check endpoint in about 2 minutes, and my send-email function in less than an hour.
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.
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
Pros of AWS Lambda
- No infrastructure129
- Cheap83
- Quick70
- Stateless59
- No deploy, no server, great sleep47
- AWS Lambda went down taking many sites with it12
- Event Driven Governance6
- Extensive API6
- Auto scale and cost effective6
- Easy to deploy6
- VPC Support5
- Integrated with various AWS services3
Pros of FaaS
- Simple way to build serverless applications1
Sign up to add or upvote prosMake informed product decisions
Cons of AWS Lambda
- Cant execute ruby or go7
- Compute time limited3
- Can't execute PHP w/o significant effort1
Cons of FaaS
Sign up to add or upvote consMake informed product decisions
What is AWS Lambda?
What is FaaS?
Need advice about which tool to choose?Ask the StackShare community!
What companies use FaaS?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS Lambda?
What tools integrate with FaaS?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+47
+43
+26
+23+42