Pieter de Bruin (Microsoft) - Welke technologie gebruiken bij implementatie Microservices?

3. Platform Services
Security &
Management
Infrastructure Services
Web Apps
Mobile
Apps
API
Management
API
Apps
Logic
Apps
Notification
Hubs
Content Delivery
Network (CDN)
Media
Services
HDInsight Machine
Learning
Stream
Analytics
Data
Factory
Event
Hubs
Mobile
Engagement
Active
Directory
Multi-Factor
Authentication
Automation
Portal
Key Vault
Biztalk
Services
Hybrid
Connections
Service
Bus
Storage
Queues
Store /
Marketplace
Hybrid
Operations
Backup
StorSimple
Site
Recovery
Import/Export
SQL
Database
DocumentDB
Redis
Cache Search
Tables
SQL Data
Warehouse
Azure AD
Connect Health
AD Privileged
Identity
Management
Operational
Insights
Cloud
Services
Batch Remote App
Service
Fabric Visual Studio
Application
Insights
Azure SDK
Team Project
VM Image Gallery
& VM Depot

4. AZURE REGIONS

5. Enterprise
proven
Hybrid
Hyper-scale
Hybrid
Hybrid
Azure Stack
On-premises

6. Enterprise
proven
Hybrid
Hyper-scale
Open + Flexible
Open &
flexible Applications
Infrastructure
Management
Databases & Middleware
App Frameworks
Linux

7. Enterprise
proven
Hybrid
Hyper-scale
Open &
flexible
Trustworthy
More compliance certifications
than any other cloud
Trustworthy
Developer & IT
productivity
Trustworthy
Platform for SaaS
extensibility

10. Choose your Editors
and Tools
Open Source
with Contributions Cross-PlatformOSS
Seamless transition
from on-premises to cloud
Faster Development CycleTotally Modular
Fast

11. .NET Framework 4.6 .NET Core 5
Full .NET Framework for any scenario and
library support on Windows
Modular libraries & runtime optimized for
server and cloud workloads

15. •
•
•
•
• Avoid “It works on my machine”
• Write once run anywhere
• Very lightweight
• Massive Scale
• Repeatable and reliable execution
• Dev Ops
• Great for microservices

16. Windows



Quotas
and limits
Process
State
isolation
Hostile
Multi-tenant Isolation
Hardware
virtualization
Job
Objects
Windows
Server
Containers
Hyper-V
Containers
Hyper-V
Virtual
Machines
Faster and more efficient More isolated and more secure
New

17. Container ImagesContainer Run-Time Image Repository

19. Agent

22. Azure Cloud Services
(Web and Worker Roles)
Azure Service Fabric
(Stateless, stateful or Actor services)
• 1 service instance per VM with uneven workloads
• Lower compute density
• Slow in deployment & upgrades
• Slower in scaling and disaster recovery
• Many microservices per VM
• High microservices density
• Fast deployment & upgrades
• Fast scaling microservices across the cluster

29. Usually stateless
microservice
with related remote
external database,
SQL DB, DocDB, etc.
Like stateless service plus
Data is in-memory and/or
persisted locally.
Data is replicated across
the Service Fabric cluster to
other nodes
Stateful service
Sample Scenarios
• Traditional WebApp or Service (even monolithic approach)
• Stateless microservice with related external DB
• Large/complex enterprise applications based on microservices
• Domain-Driven Design scenario evolution
• Stateless background service for batch/scheduled processes
Sample Scenarios
• Stateful microservice with fast data processing because
of no latency between logic and data
• Gaming backends
• Live IoT backends
• High scalable/available database implementation
(i.e. Azure Document DB, Azure SQL DB)
• Other..
Stateless service
.NET process (currently)
Any other language in
the future (Node.js, Java,
etc.)