DDD & Microservices: At Last, Some Boundaries! • Eric Evans • GOTO 2015
Why Stack Overflow recommends it
Stack Overflow users link it when answering questions about how to size and split microservices, since it ties a microservice's scope to a DDD bounded context.
Recommended by 4 people across 4 different months, 2016 to 2020.
What it is
Eric Evans, author of Domain-Driven Design, gives a conference talk at GOTO Berlin 2015 on how microservices and DDD's Bounded Context idea fit together. He argues that microservice isolation creates practical boundaries where modeling and design can thrive.
What people said
Recommends hellxcz · 2016-11 · Stack Overflow · on “Splitting and naming Microservices”
Eric Evans on GOTO 2015 conference ( [this video] ) and I 100% agree with him, answered to your question. Microservice scope should be one or maybe more Bounded Context(s). Including its supporting classes for persistence, REST/HTTP API, etc. As I understood, the microservice is deployment wrapper over Bounded Context, with adding the isolation, scaling and resilient aspects. As you wrote, you didn't apply Strategic Design to define bounded context. So its time to check, before tearing the app to parts.
Recommends masted · 2017-03 · Stack Overflow · on “Sizing up Microservices using bonded context from DDD”
I have a guess, that you're heard a reference on the talk of Eric Evans on GOTO 2015 about strategic design and microservices, so you may want to watch this capture at first: [this video] This topic also was covered by him in a further talk: [LINK]
Recommends MeTitus · 2018-05 · Stack Overflow · on “microservice shared domain layer”
My question is: What's the boundary of shared items for microservices and how bad is that? Up until a few years ago it was complicated to get the boundaries a microservice defined because there was simply no agreement on how to archieve that, but Evans sorted that out a few years ago: GOTO 2015 • DDD & Microservices: At Last, Some Boundaries! • Eric Evans [this video] Microservices also follow the four tenants of SOA and the same 9 fallacies of distributed system are to take in consideration nevertheless their business scopes are different. Bear in mind that a microservice architecture should follow a Shared-nothing sort of architecture, so services don't really share entities, what they do is su
Recommends Eben Roux · 2020-08 · Stack Overflow · on “DDD with Microservices and Multiple inputs via REST and Message Queue”
For some background I would suggest watching DDD & Microservices: At Last, Some Boundaries! [this video] by Eric Evans. A bounded context is the micro service. How you surface it is another matter. What you describe seems to be what I actually do quite frequently. I have an Identity & Access [LINK] open source project that I'm working on (so depending on when you read this it may be in a different state) that demonstrates this structure. Internal to an organization one may access the BC either via a service bus or via the web-api. External parties would utilize only the web-api as messaging should not be exposed. The web-api either returns data from the query layer or sends commands via the servi