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

AWS Lambda

24.2K
18.7K
+ 1
432
Azure Cosmos DB

595
1.1K
+ 1
130
Add tool

AWS Lambda vs Azure Cosmos DB: What are the differences?

Developers describe AWS Lambda as "Automatically run code in response to modifications to objects in Amazon S3 buckets, messages in Kinesis streams, or updates in DynamoDB". 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. On the other hand, Azure Cosmos DB is detailed as "A fully-managed, globally distributed NoSQL database service". Azure DocumentDB is a fully managed NoSQL database service built for fast and predictable performance, high availability, elastic scaling, global distribution, and ease of development.

AWS Lambda can be classified as a tool in the "Serverless / Task Processing" category, while Azure Cosmos DB is grouped under "NoSQL Database as a Service".

Some of the features offered by AWS Lambda are:

  • Extend other AWS services with custom logic
  • Build custom back-end services
  • Completely Automated Administration

On the other hand, Azure Cosmos DB provides the following key features:

  • Fully managed with 99.99% Availability SLA
  • Elastically and highly scalable (both throughput and storage)
  • Predictable low latency: <10ms @ P99 reads and <15ms @ P99 fully-indexed writes

"No infrastructure" is the top reason why over 121 developers like AWS Lambda, while over 13 developers mention "Best-of-breed NoSQL features" as the leading cause for choosing Azure Cosmos DB.

According to the StackShare community, AWS Lambda has a broader approval, being mentioned in 1022 company stacks & 612 developers stacks; compared to Azure Cosmos DB, which is listed in 24 company stacks and 24 developer stacks.

Decisions about AWS Lambda and Azure Cosmos DB
Tim Nolet

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
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of AWS Lambda
Pros of Azure Cosmos DB
  • 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
  • 28
    Best-of-breed NoSQL features
  • 22
    High scalability
  • 15
    Globally distributed
  • 14
    Automatic indexing over flexible json data model
  • 10
    Tunable consistency
  • 10
    Always on with 99.99% availability sla
  • 7
    Javascript language integrated transactions and queries
  • 6
    Predictable performance
  • 5
    High performance
  • 5
    Analytics Store
  • 2
    Rapid Development
  • 2
    No Sql
  • 2
    Auto Indexing
  • 2
    Ease of use

Sign up to add or upvote prosMake informed product decisions

Cons of AWS Lambda
Cons of Azure Cosmos DB
  • 7
    Cant execute ruby or go
  • 3
    Compute time limited
  • 1
    Can't execute PHP w/o significant effort
  • 18
    Pricing
  • 4
    Poor No SQL query support

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 Azure Cosmos DB?

Azure DocumentDB is a fully managed NoSQL database service built for fast and predictable performance, high availability, elastic scaling, global distribution, and ease of development.

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

What companies use AWS Lambda?
What companies use Azure Cosmos DB?
Manage your open source components, licenses, and vulnerabilities
Learn More

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

What tools integrate with AWS Lambda?
What tools integrate with Azure Cosmos DB?

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

Blog Posts

GitHubPythonNode.js+47
55
72925
GitHubDockerAmazon EC2+23
12
6660
JavaScriptGitHubPython+42
53
22271
What are some alternatives to AWS Lambda and Azure Cosmos DB?
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