AWS Lambda vs Azure Service Fabric: What are the differences?
What is AWS Lambda? 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.
What is Azure Service Fabric? Distributed systems platform that simplifies build, package, deploy, and management of scalable microservices apps. Azure Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices. Service Fabric addresses the significant challenges in developing and managing cloud apps.
AWS Lambda can be classified as a tool in the "Serverless / Task Processing" category, while Azure Service Fabric is grouped under "Microservices Tools".
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 Service Fabric provides the following key features:
- Simplify microservices development and application lifecycle management
- Reliably scale and orchestrate containers and microservices
- Data-aware platform for low-latency, high-throughput workloads with stateful containers or microservices
Azure Service Fabric is an open source tool with 2.57K GitHub stars and 304 GitHub forks. Here's a link to Azure Service Fabric's open source repository on GitHub.
According to the StackShare community, AWS Lambda has a broader approval, being mentioned in 1023 company stacks & 614 developers stacks; compared to Azure Service Fabric, which is listed in 6 company stacks and 3 developer stacks.
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
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
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is AWS Lambda?
What is Azure Service Fabric?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Azure Service Fabric?
Sign up to get full access to all the tool integrationsMake informed product decisions