Please enable JavaScript.
Coggle requires JavaScript to display documents.
Build microservices on Azure. 3:Identifying microservice boundaries…
Build microservices on Azure.
3:Identifying microservice boundaries
Domain model -> Microservices
Identify microservices
Aggregate
Domain service
Non-functional requirements
Bounded context
Validate design
Single responsibility
No chatty calls
Small team needed
No deployment inter-deps
Evolve independently
No problems with data consistency or integrity
Splitting service is easier than change multiple services
Application: Defining the microservices
Cross bounded context
Network overhead when direct call
Separate schema
Service as anti-corruption layer
Mediator-service when high cost cross-team communication
Non-functional
requirements
Ingestion service
when high throutput
Scheduling service
implements Load-leveling
New service when
different data storage requirements
Serverless
Delivery History service
Not part of main workflow
Event-driven workflow
Compute option
Service orchestrator
Deploying and manage
set of services
Azure platform
Kubernetes Service
Service fabric
Stateful services using
Reliable Collections
Container Service
Containers
Portability
Density
Resource isolation
Bulkhead pattern
Serverless
Azure Functions
Orchestration or
serverless
Serverless
Managability
Cost
Scalability
Orchestration
Flexibility and control
Portability
Application integration