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

AWS Lambda

17.4K
13.1K
+ 1
418
Azure Service Fabric

88
236
+ 1
25
Add tool

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.

Decisions about AWS Lambda and Azure Service Fabric
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
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of AWS Lambda
Pros of Azure Service Fabric
  • 127
    No infrastructure
  • 82
    Cheap
  • 69
    Quick
  • 57
    Stateless
  • 47
    No deploy, no server, great sleep
  • 9
    AWS Lambda went down taking many sites with it
  • 6
    Event Driven Governance
  • 5
    Auto scale and cost effective
  • 5
    Extensive API
  • 5
    Easy to deploy
  • 4
    VPC Support
  • 2
    Integrated with various AWS services
  • 5
    Intelligent, fast, reliable
  • 3
    Open source
  • 3
    Superior programming models
  • 3
    More reliable than Kubernetes
  • 3
    Runs most of Azure core services
  • 3
    Reliability
  • 2
    Quickest recovery and healing in the world
  • 1
    Deploy anywhere
  • 1
    Is data storage technology
  • 1
    Battle hardened in Azure > 10 Years

Sign up to add or upvote prosMake informed product decisions

Cons of AWS Lambda
Cons of Azure Service Fabric
  • 5
    Cant execute ruby or go
  • 0
    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

    - No public GitHub repository available -

    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 Service Fabric?

    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.

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

    What companies use AWS Lambda?
    What companies use Azure Service Fabric?
    See which teams inside your own company are using AWS Lambda or Azure Service Fabric.
    Sign up for Private StackShareLearn 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 Service Fabric?

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

    Blog Posts

    GitHubPythonNode.js+47
    50
    69765
    GitHubDockerAmazon EC2+23
    12
    6377
    JavaScriptGitHubPython+42
    52
    19992
    What are some alternatives to AWS Lambda and Azure Service Fabric?
    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