Azure Service FabricAn Extremely Gentle Introduction

Josh Lane

Agenda• Why?• What?• How?• Questions?

Why?• Monolith is traditional SOA pattern

• Coarse-grained set of services dev’ed, debugged, deployed, managed as a single atomic unit• Sits between…

• The One Database To Rule Them All• The One UI To Rule Them All

• But…• What if I want to update just one service?• What if I need to scale services independently of one another? ($$$)• What if I have mixed auth requirements for services?• What if I have mixed tech stacks amongst my services?

• Microservices are SRP for services (http://bit.ly/1PRkYfp)• Martin Fowler on microservices (http://bit.ly/1dI7ZJQ)

What Is Azure Service Fabric?• Next-gen PaaS platform• Addresses issues common to microservices architectures

• reliability• scalability• manageability (monitoring, self-healing, deployment, dev/test/prod lifecycle, etc.)• state management

• Two programming models• reliable services• reliable actors

• Two state management modes• stateful• stateless (or “stateless”)

Programming Models• Reliable Services• “Traditional” SOA-style services• More control over communication protocol• More control over partitioning scheme

• Reliable Actors• OOP on the server• Maps well to IoT domains• Smart caches, distributed networks/graphs, resource governance, etc.

• Usually a matter of style

[guitar solo]

Questions?