Explore a comprehensive conference talk on messaging and microservices delivered by Clemens Vasters, Lead Architect at Microsoft Azure Service Bus, at GOTO Amsterdam 2016. Delve into the foundational principles of service orientation and their evolution into modern microservices architecture. Learn about the challenges of centralization, the importance of autonomous services, and the benefits they bring to system design. Examine the concepts of layers, tiers, and services in the context of Microsoft Azure. Gain insights into communication patterns, directionality, symmetry, and multiplexing in microservices. Discover the significance of the edge of services, location transparency, and multi-channeling. Understand load leveling, load balancing, and messaging infrastructures. Conclude with a generalized architecture model that synthesizes these concepts for practical application in microservices development.
Overview
Syllabus
Intro
System
Service does not imply
About that API Gateway (nee ESB)
The Bus that's a Hub
Some API Gateway and ESB Promises
The Centralization Dilemma
If we'd use the ESB model on Microsoft Azure
Case-Study Microsoft Azure
Services: Autonomous Entities
Interdependencies
Why Shared Data Stores Are Bad
Data Store Decoupling Enables Evolution
Multi-Node Failover Clustering
Autonomous Services Benefits
Operational Objectives
Operational Assurances
Layers: Code Organization
Rationale for Layers
Tiers: Runtime Organization
Example: Azure Service Bus
Layers, Tiers, and Services
Communication
Client vs. Server
Directionality
Symmetry
Multiplexing
Framing, Encoding, Data Layout
Metadata
The Edge of Services
Location Transparency
Multi-Channeling
Web Sockets
Load Leveling
Load Balancing
Messaging Infrastructures
Summary: Generalized Architecture Model
Taught by
GOTO Conferences
