Serverless in Action: Event-gesteuerte Microservices - am Beispiel Azure Christian Weyer @christianweyer CTO

2 § Co-Founder & CTO at Thinktecture AG § Personal focus on § Mobile & web-based application architectures § Pragmatic end-to-end solutions § Cloud-native & serverless architectures § Independent Microsoft Regional Director § Microsoft MVP for Visual Studio Tools & Development ASPInsider, AzureInsider § Google GDE for Web Technologies § [email protected] § @christianweyer Christian Weyer Serverless in Action Event-gesteuerte Microservices - am Beispiel Azure

3 § Microservices, Nanoservices § Serverless in Azure § Azure Functions § Azure Service Bus Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Topics

How large is small? Microservices Serverless in Action Event-gesteuerte Microservices - am Beispiel Azure 4

Single Responsibility § Focused around business domain § ‘Small’ Isolation § Choice of technology § Well-defined technology-agnostic API § Mobility Autonomy § Exclusive state (data storage) Decoupling § Asynchronous communication § Really, always? Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action (Some) Principles of Microservices 5

6 End-to-End Sample – Architecture Overview Serverless in Action Event-gesteuerte Microservices - am Beispiel Azure

7 Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action End-to-End Sample – Architecture Overview

8 § Microservice: unit of independent deployment for a business domain-specific service § Nanoservice: like Microservice, but more focused & lightweight; can be replaced easier § Functions as the mental model § Make things easier, get productive earlier Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Microservices – or rather: Nanoservices

9 Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action https://twitter.com/serialseb/status/1085235076986781696

A different approach Serverless Serverless in Action Event-gesteuerte Microservices - am Beispiel Azure 10

11 § We can choose from a continuum § VM ➔ § Containers ➔ § Orchestrators ➔ § PaaS ➔ § Serverless Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Evolution to Cloud Compute Continuum PaaS IaaS On-Premises Serverless

12 Serverless Sweet Spot Programming Model § Event-driven § Stateless § Service-full Operational Model § Fully managed § Automatically scaling § Usage priced Serverless in Action Event-gesteuerte Microservices - am Beispiel Azure

13 § Serverless Compute → Azure Functions § Serverless Database → Azure Cosmos DB § Serverless Storage → Azure Storage § Serverless Realtime → Azure SignalR Service § Serverless Events → Azure Event Grid § Serverless Messaging → Azure Service Bus § Serverless Workflows → Azure Logic Apps Azure Durable Functions § Serverless IoT → Azure IoT Hub § Serverless Analytics → Azure Application Insights § Serverless Containers → Azure Container Instances Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Serverless in Azure

Azure Functions Serverless Compute Serverless in Action Event-gesteuerte Microservices - am Beispiel Azure 14

15 § Azure Functions is code being triggered by an event § Basic principles enable powerful use cases § Events ➔ Triggers § Bindings § Two ways of operation § Cost-optimized, automatic scale (aka Consumption Plan) § Always-on § V2 Runtime built on .NET Core § Available for e.g. self-hosting § Local tooling & runtime § Multiple language bindings supported Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Azure Functions: Functions-as-a-Service

16 § Incoming event triggers function § Input bindings enable easy access to data from various data sources § Output bindings offer easy access to outbound data sinks Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Functions Triggers & Bindings Your code logic Runtime Azure Function HTTP Trigge r Storage Input Binding Push Notification Output Binding Database Output Binding Email Output Binding Example

17 Functions Triggers & Bindings in Code Serverless in Action Event-gesteuerte Microservices - am Beispiel Azure

Azure Service Bus Serverless Messaging Serverless in Action Event-gesteuerte Microservices - am Beispiel Azure 18

19 § Asynchronous communication for decoupling Microservices § Different messaging services in Azure § Events, data points, messages § Event Grid § Reactive programming § Event Hubs § Big data streams § Service Bus § Enterprise-grade messaging Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Communication is Key to Cloud Architectures

20 § Queues & Topics § Reliable asynchronous communication § Rich features for temporal control § Routing and filtering § Transactions § Convoys & Sessions (related messages with state) § Bindings for Azure Functions available Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Service Bus: Messaging-as-a-Service

21 Sender § Sender sends message to queue § Queue ACKs receipt § Receiver connects to queue & retrieves message § Receiver ACKs complete (or other action) Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Service Bus Queues Receiver

22 § Sender only knows about Topic § Receivers only know about Subscriptions § Filters and Actions exist on Subscriptions Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Service Bus Topics & Subscriptions Type == ‘order‘ Sender type=quote type=order Topic Type == ‘quote‘ Filter Filter Subscrip- tion 1 Subscrip- tion 2

Summary Serverless in Action Event-gesteuerte Microservices - am Beispiel Azure 23

Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action 24 https://twitter.com/swardley/status/1024764547436085249

Single Responsibility § Focused around business domain § ‘Small’ Isolation § Choice of technology § Well-defined technology-agnostic API § Mobility Autonomy § Exclusive state (data storage) Decoupling § Asynchronous communication § Really, always? Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Principles of Microservices 25

26 § Serverless is just one option in the Cloud Continuum § Always think about the use cases and requirements § Serverless will be pre-dominant on the ‘server’ in a couple of years for many use cases § Serverless Azure tries to offer solutions in the Serverless space § Storage § Functions § Service Bus § SignalR Service & more § Azure Functions is way more than just a Web API framework Event-gesteuerte Microservices - am Beispiel Azure Serverless in Action Summary – Serverless-all-the-things?

27 Remember: there are NO servers! https://twitter.com/jeffhollan/status/1030244102082682880 Serverless in Action Event-gesteuerte Microservices - am Beispiel Azure

Chris&an Weyer, Thinktecture AG @chris&anweyer chris&[email protected] h:ps://github.com/thinktecture/serverless-microservices