[QUESTION] Models required across multiple domains about django-api-domains HOT 1 OPEN

Hello!
This is a good question, and I've dealt with a similar issue like this before, where we wanted some information usually stored in Domain B, but we wanted it regularly in Domain A.

Keep in mind that the Books/Authors example is probably a bad one for this case, because for a Human's perspective it makes sense to keep those models together.

Remember that a Domain should store information that is relevant to it, ideally within it's own Domain. Definitely if it is information you need a lot, such as the Author's name. So in your example I would see keep a copy of the Author's name in the models in the Book's Domain. This is duplicate information yes, and you'd need to keep the two Domains in sync, which is no different from the usual strategy we'd take if we had two distinct domains that needed to keep a shadow model in sync.

See this bounded context example where they are duplicating information at the boundaries of two domains, because it is cheaper to keep them in sync than to make more expensive cross-domain queries often.

from django-api-domains.