@vaughnvernon @udidahan No, I’m not thinking smaller, more along the lines of executable & self-contained as opposed to a unit of code.
1
@stilkov Then that is pretty much Bounded Context, at least according to my hammer ;)
2
1
@vaughnvernon In my interpretation, each of my … things … would contain a UI, database, external connectors, and the domain model for a BC.
1
@stilkov A Bounded Context has all those parts and for good reason, because you have a strict boundary to keep out unwanted use (think db).
1
@vaughnvernon Very interesting. Is that an accepted opinion in the DDD community? Or your interpretation?
1
@stilkov DDD Community. The Bounded Context is not JUST the domain model. Encapsulate the Ubiquitous Language & force access your way.
1
1
@vaughnvernon Excellent. I’ll find some discussion about this aspect in your book?
1
@stilkov Chapter 2 -- There is even a section on "Other Parts of the Bounded Context" or something like that.
3
@VaughnVernon @stilkov from what I have gathered @UdiDahan calls this level for autonomous components
1
1
@jeppec yes but ACs from diff BCs often deployed in same phys proc for UI composition. ACs not necessarily executable @VaughnVernon @stilkov
1
@udidahan @jeppec @vaughnvernon That was my understanding from your QCon talk back then, too. Other than that, it’s very close.
Aug 21, 2014 · 8:00 PM UTC