Lesson 125 - Managing Broad Bounded Contexts

[@Nick-db1zp]

Is a data domain pattern similar to a mixture between microservices and service-based architecture?

[@markrichards5014]

Sort of; it doesn't have to be-you can still share data in a pure microservices ecosystem with single-purpose services (service-based uses domain services that are generally coarse-grained)

[@MrPrabakar007]

👍, very useful for microserive.

[@marcom.]

I like the explanation of the data domain pattern, but I think it's not a good idea to build a static enum with all known bounded context names. This leads to a lib that knows every single bc and has to be imported from every bc. This leads to some kind of coupling and frequent dependency updates. I think with modern IDEs you don't need such a construct to find out which code uses a specific datasource.