Implementing Domain-Driven Design
Rate it:
Open Preview
Kindle Notes & Highlights
Read between April 17 - April 17, 2021
7%
Flag icon
So how do you capture this all-important Ubiquitous Language? Here are some ways that work as experimentation leads to advancement: • Draw pictures of the physical and conceptual domain and label them with names and actions.
7%
Flag icon
Create a glossary of terms with simple definitions. List alternative terms, including the ones that show promise and the ones that didn’t work, and why.
7%
Flag icon
Each Application Service method would be modified to deal with a single use case flow or user story:
Dan Kuida
(null)
8%
Flag icon
Coffee. Use that Ubiquitous Language: “Hi, Sally, I got you a tall half-skinny half-one-percent extra-hot split-quad-shot latte with whip. Do you have a few minutes to talk about . . . ?” Learn to use the Ubiquitous Language of C-Level management: “. . . profits . . . revenues . . . competitive edge . . . market domination.” Seriously. Hockey tickets.
8%
Flag icon
The onus is entirely on the client to know how to correctly commit the backlog item to a sprint.
9%
Flag icon
Do the critical path and timeline allow for any overhead required for tactical investment?
10%
Flag icon
A Core Domain is a part of the business Domain that is of primary importance to the success of the organization. Strategically speaking, the business must excel with its Core Domain.
Dan Kuida
(null)
13%
Flag icon
In fact, they were really using what amounted to DDD-Lite, employing the tactical patterns mostly for a technical payoff.
65%
Flag icon
One such straightforward approach is for a Bounded Context to expose an application programming interface (API), and another Bounded Context to use that API via remote procedure calls (RPCs).
Dan Kuida
(null)