DDD - Service Boundaries (Adam Ralph)

We know it's useful to split up complex systems. We've seen the benefits of modular deployment of microservices. Dealing with only one piece of code at a time eases our cognitive load. But how do we know where to draw the service boundaries? In complex business domains, it's often difficult to know where to start. When we get our boundaries wrong, the clock starts ticking. Before long, we hear ourselves say "it would be easier to re-write it".
Join Adam for practical advice on discovering the hidden boundaries in your systems. Help tease out the natural separation of concerns in a sample business domain. During 20 years of developing complex systems, Adam has had plenty of time to get things wrong. Learn to avoid the common pitfalls that can lead us down the path to "the big rewrite".
ABOUT ADAM
Adam is a distributed systems enthusiast and digital nomad. He works for Particular Software, the makers of NServiceBus. Adam has designed and maintained complex software systems at several companies in the finance industry. He's seen both the good and the bad that can come from applying techniques like SOA, DDD, and microservices. He also likes to speak, maintain open source projects, and fix white space rule violations.
- LinkedIn: / adamralph
- Twitter: / adamralph
- GitHub: github.com/adamralph
- Website: adamralph.com/
ADDITIONAL RESOURCES
Designing a UI for Microservices:
go.particular.net/tech-excell...
Service Oriented Architecture:
go.particular.net/tech-excell...
TECH EXCELLENCE
- Subscribe to our UA-cam channel / @techexcellence
- Join our Meetup Group www.meetup.com/techexcellence
- Follow us on LinkedIn / techexcellenceio
- Follow us on Twitter / techexcellence_
- Join our Discord Community / discord
TIMESTAMPS:
0:00 Intro
2:35 About me
5:05 DDD: Service Boundaries
1:4:23 Q&A
#ddd #soa #microservices #architecture #techexcellence

[@TechExcellence]

Designing a UI for Microservices:
go.particular.net/tech-excellence-ui-2
Service Oriented Architecture:
go.particular.net/tech-excellence-boundaries-2

[@JakeWilson88]

Thanks Adam for the awesome session!

[@TechExcellence]

You're welcome!

[@ChicagoDave44]

One thing I didn't hear you talk about is using Read Models to avoid the cross-service interactions. I have always professed that a Read Model is generally UI oriented and ignores all boundaries. Then again, I have been talking about Packaged Business Capabilities (UI + API + Data + Events all packaged as one thing) for about 6 years.

[@TechExcellence]

Here are the slides: www.dropbox.com/scl/fi/jtyb6lmscycau8axkmg5t/ddd-service-boundaries.pdf?rlkey=gxpcxtadgx7iq7c7og4orhizr&e=1&st=a6atkiny&dl=0

[@usamesavas9848]

I am 20 minutes into the video and I can tell by now that it is awesome, packed with real life examples.

[@TechExcellence]

Glad you enjoyed it!

[@georgesotiropoulos9935]

A very nice session on service boundaries and fat messages. However I still prefer to store the OrderDetails on the First Order Microservice, in one place and use a Saga and specific Commands to send specific portions of the OrderDetails Data to each of the rest Microservices in the ecommerce scenario. Otherwise we need to have extra layer of temporal persistency for each microservice (we already have a local-database at each microservice, we propably have a lookup database, and we have to deal now with a new temporary storage ), add on top to implement all these using hexagons and CQRS projecions and the code becomes really-really complex. My two cents......Great session though!