Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • It seems to me that the only thing defining separate bounded contexts is the need to differentiate linguistics and associated operational differences, i.e. it's called product in one area and product in another area but they are different, so we need two products and they both can't be in the same model (same name etc). So why don't we just change the names to represent their subtly different semantics? They we could have one model to rule them all. Subdomains are natural but I am not seeing bounded contexts at the moment. Just thinking aloud here... Commented Sep 26, 2016 at 10:23
  • I guess you already realized why it is profitable to split your domain on contexts. So what could be useful now is the right way to identify them, to define the context's boundaries. Here is how I do it: medium.com/@wrong.about/… Commented Dec 2, 2017 at 18:36