Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Fundamental Domain-Driven Design For Microservices
Search
Oliver Drotbohm
July 07, 2016
Programming
4
670
Fundamental Domain-Driven Design For Microservices
Slides of the talk I gave at Java Forum Stuttgart 2016.
#jfs2016 @springcentral
Oliver Drotbohm
July 07, 2016
Tweet
Share
More Decks by Oliver Drotbohm
See All by Oliver Drotbohm
It Takes Two to Tango – Designing Module Interactions in Modulithic Spring Applications
olivergierke
5
620
Bottom-Up Architecture – Bridging the Achitecture Code Gap
olivergierke
4
870
Spring Modulith – A Deep Dive
olivergierke
7
4.2k
Spring for the Architecturally Curious Developer
olivergierke
5
1.8k
Spring Boot 3 & Spring Framework 6
olivergierke
4
2k
Architecturally-evident Java Applications with jMolecules
olivergierke
8
2.8k
A Deep Dive into Spring Application Events
olivergierke
12
3.2k
Building Better Monoliths – Modulithic Applications with Spring Boot
olivergierke
4
940
Spring HATEOAS – Hypermedia APIs with Spring
olivergierke
1
720
Other Decks in Programming
See All in Programming
Java 24まとめ / Java 24 summary
kishida
3
500
Make Parsers Compatible Using Automata Learning
makenowjust
2
5.2k
Enterprise Web App. Development (1): Build Tool Training Ver. 5
knakagawa
1
120
AI時代の開発者評価について
ayumuu
0
180
Fiber Scheduler vs. General-Purpose Parallel Client
hayaokimura
1
110
Contribute to Comunities | React Tokyo Meetup #4 LT
sasagar
0
500
ComposeでWebアプリを作る技術
tbsten
0
120
gen_statem - OTP's Unsung Hero
whatyouhide
1
210
MCP調べてみました! / Exploring MCP
uhzz
2
2.3k
Bedrock×MCPで社内ブログ執筆文化を育てたい!
har1101
6
1k
エンジニアが挑む、限界までの越境
nealle
1
260
Jakarta EE Meets AI
ivargrimstad
0
120
Featured
See All Featured
Facilitating Awesome Meetings
lara
54
6.3k
What’s in a name? Adding method to the madness
productmarketing
PRO
22
3.4k
Designing Experiences People Love
moore
141
24k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
41
2.2k
Unsuck your backbone
ammeep
670
57k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
2.9k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
5
560
Why Our Code Smells
bkeepers
PRO
336
57k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.5k
How to Think Like a Performance Engineer
csswizardry
23
1.5k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
29
1.6k
Speed Design
sergeychernyshev
29
900
Transcript
© 2014 SpringOne 2GX. All rights reserved. Do not distribute
without permission. DOMAIN-DRIVEN DESIGN / OLIVERGIERKE ƻ
[email protected]
FUNDAMENTAL FOR MICROSERVICES
2
None
4 http://www.infoq.com/minibooks/domain-driven-design-quickly
Microservices ♥ Domain-Driven Design 5 11:10 — Beethoven Saal
6
6
Implementing Domain-Driven Design 7
Value objects 8
Stringly typed code 9 public class Customer { private Long
id; private String firstname, lastname, email; … }
Stringly typed code 10 public class SomeService { public void
createUser(String firstname, String lastname, String email) { … } }
11 public class Customer { private Long id; private Firstname
firstname; private Lastname lastname; private EmailAddress emailAddress; … }
Value Objects are a PITA to build in some languages.
12
Still, they’re worth it. 13 See „Power Use of Value
Objects in DDD“ by Dan Bergh Johnsson.
Lombok — putting the spice back into Java. 14
15 @Value public class Customer { UUID id = UUID.randomUUID();
Firstname firstname; Lastname lastname; EmailAddress email; @Value static class EmailAddress { String value; } }
AutoValue 16 Project website on GitHub.
Entities & Aggregates 17
18 Order LineItem Product Invoice Customer Payment Address Email
18 Order LineItem Product Invoice Customer Payment Address Email
Persistence technology VS. Domain model 19
Aggregate = Entity + Repository 20
21 Order LineItem Product Invoice Customer Payment Address Email
Bounded Context 22
Order LineItem Product Invoice Customer Payment Address
24 Shipping Accounting Catalog Orders User Registration
24 Shipping Accounting Catalog Orders User Registration Accounting Payment information
Billing Address Shipping Shipping address Customer Product
Domain-Driven Design & Monoliths 25
Avoid technologies that get in your way. 26
How to enforce context boundaries? 27
What about consistency? 28
References between Bounded Contexts? 29
Domain Events 30
31 Level 0: No events at all
31 Level 0: No events at all Level 1: Explicit
operations
If you’re calling two setters in a row, you’re missing
a concept. 32
33 Level 0: No events at all Level 1: Explicit
operations Level 2: Some operations as events
State transitions become domain events. 34
35 Level 0: No events at all Level 1: Explicit
operations Level 2: Some operations as events Level 3: Event Sourcing
Domain-Driven Design & Microservices 36
Bounded contexts define system boundaries. 37
38 Shipping Accounting Catalog Orders User Registration Accounting Payment information
Billing Address Shipping Shipping address Customer Product
39 Shipping Accounting Catalog Orders User Registration Accounting Shipping
40 Shipping Accounting Catalog Orders User Registration Accounting Shipping HTTP
Messaging
Architecture is less likely to deteriorate as it’s harder to
violate boundaries. 41
Restructuring service boundaries is much harder. 42
Inter-Service communication becomes remote communication. 43
Accept and embrace eventual consistency between services. 44
Domain Events 45
REST & Messaging 46
Domain events become state transitions. 47
Hypermedia for state transition and explicit events. 48
Thanks! 49