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

AWS Lambda

23.8K
18.5K
+ 1
432
Chalice

45
107
+ 1
0
Add tool

AWS Lambda vs Chalice: What are the differences?

AWS Lambda and Chalice are both services provided by Amazon Web Services (AWS) for serverless computing. While they have similarities, there are several key differences between the two.

  1. Pricing and Usage: One key difference between AWS Lambda and Chalice is the pricing model and usage. AWS Lambda charges by the number of requests, the duration of execution, and the memory allocated. Chalice, on the other hand, is a framework that allows developers to build serverless applications on AWS Lambda, and it does not have its own pricing model. The cost of using Chalice is based on the resources consumed by the underlying Lambda functions.

  2. Deployment and Configuration: Another difference is the deployment and configuration process. With AWS Lambda, developers need to manually create and configure the Lambda functions, set up triggers, and manage the deployment process. Chalice simplifies this process by providing a command-line interface (CLI) to deploy and manage serverless applications. It automatically sets up the necessary resources and handles the deployment process.

  3. Supported Languages: AWS Lambda supports a variety of programming languages, including Node.js, Python, Java, and C#. Chalice, on the other hand, is specifically designed for Python applications. It provides a Pythonic API for building serverless applications, making it easier for Python developers to work with.

  4. Scaling and Performance: AWS Lambda automatically scales the execution environment based on the incoming requests, allowing applications to handle large workloads efficiently. Chalice leverages the scaling capabilities of AWS Lambda, so it benefits from the same scalability. However, Chalice also provides additional features, such as automatic HTTP session management and content negotiation, which can enhance the performance of serverless applications.

  5. Development and Debugging: In terms of development and debugging, AWS Lambda provides tools and features that can help developers test and troubleshoot their functions. Chalice, as a framework, provides additional capabilities for local testing and debugging. It allows developers to run serverless applications locally, making it easier to identify and fix issues during the development process.

  6. Flexibility and Customization: While AWS Lambda provides a wide range of features and options for building serverless applications, Chalice offers a higher level of abstraction and simplifies the development process. Chalice provides a set of predefined routes and handlers, making it easier to build RESTful APIs. However, this level of abstraction may limit the flexibility and customization options available to developers.

In summary, AWS Lambda is a serverless compute service provided by AWS, while Chalice is a Python framework for building serverless applications on AWS Lambda. The key differences between the two include pricing and usage models, deployment and configuration processes, supported languages, scaling and performance capabilities, development and debugging tools, and flexibility and customization options.

Advice on AWS Lambda and Chalice

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 and Chalice
Cory Bell

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.

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 Chalice
  • 129
    No infrastructure
  • 83
    Cheap
  • 70
    Quick
  • 59
    Stateless
  • 47
    No deploy, no server, great sleep
  • 12
    AWS Lambda went down taking many sites with it
  • 6
    Event Driven Governance
  • 6
    Extensive API
  • 6
    Auto scale and cost effective
  • 6
    Easy to deploy
  • 5
    VPC Support
  • 3
    Integrated with various AWS services
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of AWS Lambda
    Cons of Chalice
    • 7
      Cant execute ruby or go
    • 3
      Compute time limited
    • 1
      Can't execute PHP w/o significant effort
      Be the first to leave a con

      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 Chalice?

      The python serverless microframework for AWS allows you to quickly create and deploy applications that use Amazon API Gateway and AWS Lambda.

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

      What companies use AWS Lambda?
      What companies use Chalice?
      See which teams inside your own company are using AWS Lambda or Chalice.
      Sign up for StackShare EnterpriseLearn More

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

      What tools integrate with AWS Lambda?
      What tools integrate with Chalice?

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

      Blog Posts

      GitHubPythonNode.js+47
      55
      72482
      GitHubDockerAmazon EC2+23
      12
      6582
      JavaScriptGitHubPython+42
      53
      21982
      What are some alternatives to AWS Lambda and Chalice?
      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