Need advice about which tool to choose?Ask the StackShare community!
AWS Lambda vs MongoLab: 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, MongoLab is detailed as "Database-as-a-Service for MongoDB". mLab is the largest cloud MongoDB service in the world, hosting over a half million deployments on AWS, Azure, and Google.
AWS Lambda belongs to "Serverless / Task Processing" category of the tech stack, while MongoLab can be primarily classified under "MongoDB Hosting".
"No infrastructure" is the top reason why over 121 developers like AWS Lambda, while over 60 developers mention "Development free tier" as the leading cause for choosing MongoLab.
9GAG, Asana, and CircleCI are some of the popular companies that use AWS Lambda, whereas MongoLab is used by Lyft, Rocket.Chat, and Hinge. AWS Lambda has a broader approval, being mentioned in 1022 company stacks & 612 developers stacks; compared to MongoLab, which is listed in 102 company stacks and 40 developer stacks.
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 MongoLab
- Development free tier61
- Easy setup46
- Scalable mongo hosting38
- Heroku plugin25
- REST API14
- High availability9
- Geospatial support9
- Replication and backups5
- Premium support5
- Multi-cloud2
- Largest and most experienced1
- Azure Add-on1
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 MongoLab
- Lab bought by MongoDB. Being replaced by Atlas1
Sign up to add or upvote consMake informed product decisions
What is AWS Lambda?
What is MongoLab?
Need advice about which tool to choose?Ask the StackShare community!
What companies use MongoLab?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS Lambda?
What tools integrate with MongoLab?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+47
+43
+26
+23+42