I have a project in which I have to manage projects, invoices and orders to providers. So I think that I can define three bounded context.
First bounded context: Projects.Second bounded context: Invoices.Third bounded context: Orders to providers.
Well, my doubt is how to the invoices of a project, because they are different bounded contexts.
I think that a project shouldn't have a reference to the ID of the invoice aggregate root, because really the invoce it is not needed for the logic of the projects, just to know the relation between them. But I am not sure if this is correct and I could have this relation.
But if this solution is correct, then to know to which project an invoice belongs to, should I have a reference to the ID of the project? Because really for me a project is not more important than invoice so I am not sure if it correct to say an invoce is part of the project.
Or perhaps another solution it would be to define an entity invoices (or value object) in the project bounded context to stablish the relationship and an entity or value object Project in the bounded context of invoices.
Or perhaps did I define incorrectly my bounded context?
Perhaps it is a bit generic question, but the main point it how to stablish the relation between two aggregate roots from different bounded conetxts, of perhaps, in this case, it is a bad design.
Thanks so much.