Splitting a system into microservices is a challenging task. This talk shows how ideas like Bounded Context, migration scenarios and technical constraints can be used to build a microservice architecture. Held at WJAX 2016.
6. Microservices:
Definition
> No consistent definition
> Microservices are modules
> Independent deployment units
> E.g. Docker container
> Microservice owned by one team
9. Why is the Split so
Important?
> Microservices implement a part of the logic
> Allow isolated development of features
> …and independent teams
> If split is wrong, you won’t achieve goals.
> …and there is just more complexity.
> But there are even more goals!
10. Why Microservices?
Strong Modularization
Scaling Agile
Sustainable development
Replaceable Services
Continuous Delivery
Free choice of technology
Handle Legacy efficient
Independent Scaling
Robustness
Small teams develop and
deploy independently
Add services – not code
Small Services
Failure limited to single
Microservice
11. Why Microservices?
Scaling Agile
Sustainable development
Continuous Delivery
Free choice of technology
Handle Legacy efficient
Independent Scaling
Robustness
Organization
Deployment
Units
Technology
31. Why would you build
a universal data
model if that is
neither possible nor
useful??
32. Bounded Context:
Challenge
> Not a way to design a great architecture
> …but consequence of good domain
architecture
> i.e. clearly separated domains will lead to
separated BOUNDED CONTEXTS
> …containing logic and data
> How can you find BOUNDED CONTEXTS?
34. Divide by Use Cases
> Microservice should implement a use case
> …ideally without calling other microservices
> Divide use cases among microservices
> …then decide about the BOUNDED CONTEXT
35. BrowsingRegistration
Creating Microservices
User Registration Search Products
by Keywords
Browse Products
by Category
Checkout
Payment
Define ShipmentUpdate Profile
Basic customer
data
Preferences
Recommendations
Billing address
Payment
information
All these services have data about the customer!!
36. Bounded Context
Scaling Agile
Sustainable development
Continuous Delivery
Free choice of technology
Handle Legacy efficient
Independent Scaling
Robustness
Organization
Deployment
Units
Technology
41. Bounded Contexts
> Browsing distributed in many artifacts
> Change to Browsing might influence all of
them
> …or not
> BOUNDED CONTEXTS would be desirable
42. Migrate to Bounded Context
Product Customer Warehouse
Product
Service
Customer
Service
Warehouse
Service
iOS Android PoS Web
BrowsingBrowsing
43. Introducing
Bounded Contexts
> …would change the architecture completely
> …might be very hard
> …and risky
> Is it worth it?
> Is it even doable?
> Might also change the organization
45. Add services
Product Customer Warehouse
Product
Service
Customer
Service
Warehouse
Service
iOS Android PoS Web
News-
letter
Web
46. Add Service
> Might replace the old system stepwise
> Immediate benefits
> Low risk
> Major reason for microservices
47. Cut existing services
Product Customer Warehouse
Product
Service
Customer
Service
Warehouse
Service
iOS Android PoS Web
48. Existing Architecture
Scaling Agile
Sustainable development
Continuous Delivery
Free choice of technology
Handle Legacy efficient
Independent Scaling
Robustness
Organization
Deployment
Units
Technology
49. Existing Architecture
> ...has an impact on the target architecture
> What good is an architecture you cannot
migrate into?
> Might overrule everything else
> Even BOUNDED CONTEXT
50. BrowsingRegistration
External Systems
User Registration Search Products
by Keywords
Browse Products
by Category
Checkout
Payment
Define ShipmentUpdate Profile Browse Products
by Category
Payment
Provider
Logistic
Partner
52. External Systems
> Limit integration for each external system to
one Microservice
> External system might belong to a domain
> …or BOUNDED CONTEXT
> ...or not
> Simplifies integration
> Easier to achieve robustness
53. External Systems
Scaling Agile
Sustainable development
Continuous Delivery
Free choice of technology
Handle Legacy efficient
Independent Scaling
Robustness
Organization
Deployment
Units
Technology
57. Technical Reasons
> Independent scalability is just one technical
reason
> There are many more
> Might be OK to share database in this
scenario
> Might even split read and write
58. CQRS
> Command – Query Responsibility
Segregation
> Commands change data
> Query provide data
> Implement in separate microservices
68. EMail slideswjax2016@ewolff.com to get:
Slides
+ Microservices Primer
+ Sample Microservices Book
+ Sample of Continuous Delivery Book
Powered by Amazon Lambda & Microservices