Compares Amazon Lambda with Azure Servie Fabric on running Microservices

1. Micro-Services
with AWS Lambda and Azure Service Fabric

2. Microservices

3. Small autonomous services
working together

4. Modelled Around
Business Domain
Culture Of
Automation Hide Implementation
Details
Decentralise All
The Thins
Deploy
Independently
Consumer FirstIsolate Failure
Highly
Observable

5. avoid solving complex
infrastructure problems

6. Azure Service Fabric

8. • 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

11. • 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

13. Functional More OO
Philosophie

14. Common
High-availability
Built-in Fault Tolerance
Automatic scaling
Integrated Security
Monitor and logging

15. Stateless Stateless & Statefull
State

16. External Integrated
Persistance

17. External Integrated
Reliable Messaging

18. Java, Node.js
and Python
Java, Node.js
and .NET
Languages

19. AWS only Azure, Azure Stack,
Windows and Linux
(Cloud and On-premises)
Environments

20. General Opinionated
(for Microservices)
Use

21. External Tool Integrated
Deployment

22. 0 - ??? 300 - ???
Cost / Month

24. Thank You!
Paul Affentranger
affentranger@afca.ch
www.afca.ch