DDD - Service Boundaries (Adam Ralph)

[@alpsavasdev]

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!

[@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.

[@JakeWilson88]

Thanks Adam for the awesome session!

[@TechExcellence]

You're welcome!

[@TechExcellence]

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

[@BlindVirtuoso]

This is excellent one.

[@TechExcellence]

Thank you!

[@TechExcellence]

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

[@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!