Overview

AWS Lambda

Stacks24.4K

Followers18.8K

Votes432

Azure Service Fabric

Stacks105

Followers284

Votes26

GitHub Stars3.0K

Forks399

AWS Lambda vs Azure Service Fabric: What are the differences?

Deployment and Scaling: AWS Lambda is a serverless computing service where the infrastructure is managed by AWS, allowing developers to focus on writing code without worrying about server management. Azure Service Fabric, on the other hand, is a microservices platform that provides more control over deployment and scaling, making it suitable for complex applications that require fine-tuning of resources.
Programming Languages: AWS Lambda supports a variety of programming languages such as Node.js, Python, Java, and C#, while Azure Service Fabric has wider language support due to its ability to work with any language that can be compiled to a .NET assembly, giving developers more flexibility in language choice.
Pricing Model: AWS Lambda follows a pay-as-you-go pricing model based on the number of requests and execution time, making it cost-effective for sporadic workloads. In contrast, Azure Service Fabric requires a monthly fee per virtual machine, potentially resulting in higher costs for sustained and resource-intensive applications.
High Availability: AWS Lambda automatically scales the infrastructure to handle incoming requests, ensuring high availability without user intervention. Azure Service Fabric provides high availability through its built-in stateful and stateless services, allowing developers to design applications that can withstand failures and maintain uptime.
Development Environment: AWS Lambda provides a simple development environment with limited debugging capabilities, making it suitable for quick prototyping and testing. Azure Service Fabric offers a more comprehensive development environment with rich debugging tools and integration with Visual Studio, ideal for complex applications that require thorough testing and debugging.
Integration with Other Services: AWS Lambda seamlessly integrates with various AWS services such as S3, DynamoDB, and API Gateway, enabling developers to build serverless architectures. Azure Service Fabric integrates well with other Azure services, providing a cohesive ecosystem for building and deploying applications that leverage Azure's infrastructure.

In Summary, AWS Lambda is a serverless computing service with automated scalability, while Azure Service Fabric is a microservices platform offering more control over deployment and scaling.

Advice on AWS Lambda, Azure Service Fabric

Tim

CTO at Checkly Inc.

Sep 18, 2019

Needs adviceon

Heroku

AWS Lambda

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

357k views357k

Comments

Detailed Comparison

AWS Lambda	Azure Service Fabric
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.	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.
Extend other AWS services with custom logic;Build custom back-end services;Completely Automated Administration;Built-in Fault Tolerance;Automatic Scaling;Integrated Security Model;Bring Your Own Code;Pay Per Use;Flexible Resource Model	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; Run anything – your choice of languages and programming models; Run anywhere – supports Windows/Linux in Azure, on-premises, or other clouds; Scales up to thousands of machines
Statistics
GitHub Stars -	GitHub Stars 3.0K
GitHub Forks -	GitHub Forks 399
Stacks 24.4K	Stacks 105
Followers 18.8K	Followers 284
Votes 432	Votes 26
Pros & Cons
Pros 129 No infrastructure 83 Cheap 70 Quick 59 Stateless 47 No deploy, no server, great sleep Cons 7 Cant execute ruby or go 3 Compute time limited 1 Can't execute PHP w/o significant effort	Pros 5 Intelligent, fast, reliable 4 Runs most of Azure core services 3 Open source 3 Reliability 3 Superior programming models

What are some alternatives to AWS Lambda, Azure Service Fabric?

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.

Google Cloud Run

A managed compute platform that enables you to run stateless containers that are invocable via HTTP requests. It's serverless by abstracting away all infrastructure management.

Istio

Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc.

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.

Google Cloud Functions

Construct applications from bite-sized business logic billed to the nearest 100 milliseconds, only while your code is running

Knative

Knative provides a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center

OpenFaaS

Serverless Functions Made Simple for Docker and Kubernetes

Moleculer

It is a fault tolerant framework. It has built-in load balancer, circuit breaker, retries, timeout and bulkhead features. It is open source and free of charge project.

Nuclio

nuclio is portable across IoT devices, laptops, on-premises datacenters and cloud deployments, eliminating cloud lock-ins and enabling hybrid solutions.

Express Gateway

A cloud-native microservices gateway completely configurable and extensible through JavaScript/Node.js built for ALL platforms and languages. Enterprise features are FREE thanks to the power of 3K+ ExpressJS battle hardened modules.