Need advice about which tool to choose?Ask the StackShare community!
AWS Lambda vs MongoDB Stitch: What are the differences?
Introduction: In the world of cloud computing, AWS Lambda and MongoDB Stitch are two popular serverless computing solutions that offer different capabilities and features. Below are the key differences between AWS Lambda and MongoDB Stitch.
Programming Languages Supported: AWS Lambda supports a variety of programming languages such as Node.js, Python, Java, and C#. In contrast, MongoDB Stitch primarily supports JavaScript and TypeScript for creating serverless functions. This difference in language support can influence the development team's choice based on their familiarity and expertise with a particular language.
Database Integration: MongoDB Stitch is specifically designed to integrate seamlessly with MongoDB databases, allowing developers to easily access and manipulate data stored in MongoDB collections. On the other hand, AWS Lambda provides more flexibility in terms of database integration, allowing developers to connect to various databases like Amazon DynamoDB, Amazon RDS, and others. The choice between AWS Lambda and MongoDB Stitch may depend on the preferred database system and the complexity of data operations required.
Pricing Model: AWS Lambda follows a pay-as-you-go pricing model, where users are charged based on the number of requests and the duration of code execution. MongoDB Stitch offers a free tier with limited resources and charges based on the number of invocations and data transfer. Depending on the scale and usage patterns of the application, developers can choose the pricing model that aligns with their budget and requirements.
Vendor Lock-in: AWS Lambda is a service provided by Amazon Web Services (AWS), which may lead to potential vendor lock-in for organizations heavily invested in the AWS ecosystem. MongoDB Stitch, on the other hand, provides more flexibility in terms of deployment options, as it can be integrated with various cloud platforms and on-premises environments, reducing the risk of vendor lock-in. This difference can be a crucial factor for organizations looking to maintain portability and avoid dependency on a single cloud provider.
Event Triggers: AWS Lambda offers a wide range of event sources for triggering serverless functions, including API Gateway, S3, DynamoDB, and more. In comparison, MongoDB Stitch has more limited event trigger options, mainly focusing on database changes within MongoDB collections. Depending on the application's requirements and the need for diverse event sources, developers can choose between AWS Lambda and MongoDB Stitch for event-driven architecture implementations.
Summary: In summary, AWS Lambda and MongoDB Stitch differ in terms of programming language support, database integration, pricing model, vendor lock-in considerations, and event trigger options, providing developers with a range of factors to consider when choosing a serverless computing solution.
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 MongoDB Stitch
- Static Hosting2
- Serverless1
- Best integration with MongoDB (Atlas)1
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