I'm here for some advice about how to manage the situation where I have a legacy application running locally on an onpremise server with it's own database and I'm about to add an online shop app to it. I have created a new domain model for the context and added an anti corruption layer (ACL) to convert the data. This ACL will reside in a windows service that communicates via queues with the main online shop app to keep the data in sync and register the successful transactions into the legacy db.
so the whole can be schematized like that:
LegacyApp <- ACL <- WinService <-queue-> CloudApp
- Could it be right to consider the windows service and the cloud app as parts of the same bounded context, or should each be represented by it's own bounded context ?
- If so, having the domain model shared, the communication over the queue should in your opinion be based on DTO's or directly serializing the aggregates?