From the course: Software Architecture: Domain-Driven Design
Join today to access over 22,700 courses taught by industry experts or purchase this course individually.
Same name, different entity
From the course: Software Architecture: Domain-Driven Design
Same name, different entity
- [Instructor] Now let's take that picture we were just looking at and think of it in terms of the implementation or the data model. If you were thinking about data, in particular if you're thinking about a traditional way of building a system, where you think about the data model first, you're probably thinking in terms of normalization and relational databases. And in that kind of world, when you look at modeling the way the entities look, you'd end up with a picture that looks rather like this one. You'd have context that contain things that are obviously within that context, but outside of the context, you'd have entities that were independent, that somehow had to work in multiple contexts at the same time. In a domain driven design world, that's considered a bad thing is that every entity should be associated with some context or another. Now getting back to the ubiquitous language issue, you'll remember that…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.