Need advice about which tool to choose?Ask the StackShare community!
AWS Lambda vs Chalice vs Zappa: What are the differences?
1. Deployment Method: AWS Lambda requires you to manually deploy your functions, whereas Chalice and Zappa enables simpler deployment through the use of command-line tools. 2. Integration with API Gateway: Chalice and Zappa provide seamless integration with API Gateway, streamlining the process of creating RESTful APIs, whereas with AWS Lambda, you have to configure API Gateway separately for integrating with APIs. 3. Framework Support: Chalice and Zappa are built on top of frameworks (Flask and Django, respectively), providing a more structured approach to building serverless applications, while AWS Lambda does not offer a specific framework for building applications. 4. Auto-Scaling Configuration: AWS Lambda handles auto-scaling and resource provisioning automatically, based on the incoming traffic, while Chalice and Zappa require manual configuration for auto-scaling and resource management. 5. Resource Management: Chalice and Zappa allow you to manage AWS resources directly from within the framework, simplifying resource allocation and maintenance tasks, whereas with AWS Lambda, you need to manage resources separately through the AWS Management Console or CLI. 6. Cost Management: Chalice and Zappa provide more transparent cost management by offering built-in features for monitoring and optimizing costs, while with AWS Lambda, you need to rely on third-party tools or custom solutions for effective cost management.
In Summary, AWS Lambda, Chalice, and Zappa differ in deployment methods, API Gateway integration, framework support, auto-scaling configuration, resource management, and cost management in serverless application development.
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.
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 Chalice
Pros of Zappa
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 Chalice
Cons of Zappa
Sign up to add or upvote consMake informed product decisions
What is AWS Lambda?
What is Chalice?
What is Zappa?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Chalice?
What companies use Zappa?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS Lambda?
What tools integrate with Chalice?
What tools integrate with Zappa?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+47
+43
+26
+23+42