James Coplien, talking about DCI and DDD.
-
- いいね！5
Vaughn Vernon
@VaughnVernon
Blog post buff.ly/1SCWk3g to learn how you should name "shadow concepts" across DDD Bounded Contexts.
2016-01-10 06:16:12
Atsuhiro Kubo
@iteman
"Tenant" seems an "informational model". "Company" seems a "physical world model". phpmentors.jp/post/135566074… #DDDesign twitter.com/VaughnVernon/s…
2016-01-13 12:23:16
Atsuhiro Kubo
@iteman
From the point of view of DCI, I think "Tenant" can be viewed as an entity, "Company" and "Subscriber" are roles.
2016-01-13 12:34:50
Atsuhiro Kubo
@iteman
実践ドメイン駆動設計の Tenant のようなコンテキストをまたがるドメインモデルって、フレームワークだと思う。フレームワークが提供するドメインモデルが、対象ドメインの語彙になるならそのまま使えばよい。 github.com/phpmentors-jp/…
2016-01-13 13:17:19
Atsuhiro Kubo
@iteman
DCI は、ジェネレーティブドメインモデルの Bounded Context におけるローカル化技術として使うことができる、という見方はどうだろう。 twitter.com/jcoplien/statu…
2016-01-13 13:32:41
Daniel Speicher
@dsp_de
@iteman @jcoplien @andrzejkrzywda Context boundary (DCI) = b. of use case << C.b. (DDD) = b. of controllable conceptual consistency.
2016-01-18 19:45:11
James Coplien
@jcoplien
@dsp_de @iteman @andrzejkrzywda But I know no DDD concept that can characterise DCI Contexts. DDD is largely static; DCI both dynamic&static
2016-01-20 03:45:04
James Coplien
@jcoplien
@dsp_de @iteman @andrzejkrzywda I hope that Eric & I can catch up and settle a bit of vocabulary, to help people, at DDD Europe. #DDDEU
2016-01-20 03:47:12
James Coplien
@jcoplien
Ratcheting up DDD to DCI. DDD 2016 Belgium #DDDEU. Learn DCI from the experts & add dynamics to your DDD—27 January. dddeurope.com/jim-coplien-dc…
2016-01-20 06:02:35
James Coplien
@jcoplien
@iteman Yes—reducing domains to modules reflects a simple, hierarchical worldview. It's all about coding the interactions between domains.
2016-01-20 06:23:00Talk: Symmetry in Design - JIM COPLIEN - Domain-Driven Design Europe
http://dddeurope.com/jim-coplien.html
DDD is rooted in symmetry — i.e., in a hierarchical model of the world into disjoint sets. We know (in fact, one can formally prove) that the world is not so simple. This means that while DDD may lead to a good top-level architecture, the details must almost always break symmetry locally. This in fact is the foundation of patterns and is also the foundation of most popular programming languages' feature sets. It further explains why popular programming languages are “messy.” This talk gives pointers on how to mix symmetry and symmetry-breaking in design by combining DDD, object-orientation, patterns, and DCI, and give an intuitive glimpse of the unifying formalisms that tie them together.