Context: You build your system as a collection of small, independent systems, each with its own UI, data, and logic. What do you call them?
22
2
@stilkov Bounded Context
1
@vaughnvernon A strong relation, I agree, but not the same thing.
1
@stilkov If you are thinking smaller than Bounded Context, perhaps @UdiDahan would call these "Business Components," and there could be many
1
@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
Replying to @VaughnVernon
@vaughnvernon Excellent. I’ll find some discussion about this aspect in your book?

Aug 21, 2014 · 4:45 PM UTC

1
Replying to @stilkov
@stilkov Chapter 2 -- There is even a section on "Other Parts of the Bounded Context" or something like that.
3
@vaughnvernon Excellent. Will grab it from the office library on my way home :-)