Upload
paul-affentranger
View
298
Download
7
Embed Size (px)
Citation preview
Micro-Serviceswith AWS Lambda and Azure Service Fabric
Microservices
Small autonomous services working together
Modelled AroundBusiness Domain
Culture OfAutomation Hide Implementation
Details
Decentralise AllThe Thins
DeployIndependently
Consumer FirstIsolate Failure
HighlyObservable
avoid solving complex infrastructure problems
Azure Service Fabric
• 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
• 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
Functional More OO
Philosophie
Common
High-availabilityBuilt-in Fault Tolerance
Automatic scalingIntegrated Security
Monitor and logging
Stateless Stateless & Statefull
State
External Integrated
Persistance
External Integrated
Reliable Messaging
Java, Node.js and Python
Java, Node.jsand .NET
Languages
AWS only Azure, Azure Stack, Windows and Linux
(Cloud and On-premises)
Environments
General Opinionated(for Microservices)
Use
External Tool Integrated
Deployment
0 - ??? 300 - ???
Cost / Month