Compared: Microservices with AWS Lambda and Azure Service Fabric

From the deck on Microservices with AWS Lambda and Azure Service Fabric by Paul Affentranger

AWS Lambda Azure Service Fabric
Features • Functional approach
• Stateless
• “Serverless” compute service
• Runs code on events
• Extends AWS services
• Provides back-end service
• High-availability
• Built-in Fault Tolerance
• Automatic scaling
• Integrated Security Model
• Java, Node.js, and Python
• Massively scalable
• Self-healing
• Programmming in .NET, Java or node.js.
• Stateless and stateful
• Actor Model
• Highly reliable.
• Simplify by stateful microservices in place of caches
• Deploy to Azure or to on-premises clouds
• Running on Windows or Linux
• Develop with a "datacenter on your machine"
• Deploy support
• Applications at higher density
• Different Versions side by side
• Manage lifecycle without downtime
• Upgrade independently
• Monitor and diagnose
• Scale up or scale down your cluster Azure Service Fabric
Philosophy Functional More OO
State Stateless Stateless & Stateful
Persistence External Integrated
Reliable Messaging External Integrated
Languages Java, Node.js and Python Java, Node.js and .NET
Environments AWS only Azure, Azure Stack, Windows and Linux (Cloud and On-premises)
Use General Opinionated (for Microservices)
Deployment External Tool Integrated

What they have in common:
  • High-availability
  • Built-in Fault Tolerance
  • Automatic scaling
  • Integrated Security
  • Monitoring and logging

Comments