I'm getting ready to create an integration with a major external system and was wondering if my understanding of the design pattern for this in domain driven design was solid.
External System serves SOAP, mine's a web api 2 solution.
Full CRUD operations across many SOAP methods
- Create a giant facade class that receives the data.
- Have each method in the facade call an adapter that then transforms the data from SOAP to a domain model.
- Call the adapter in infrastructure service class and pass it up into the domain.
Concerns: Does this pattern sound correct? Is there a more fitting one for creating a clearly defined bounded context?
I'd be using infrastructure as a pass through to the domain, it wouldn't be doing much at this point, another option is to pass the adapter directly to a factory though I prefer going through infrastructure.
Conceptual Diagram I'm basing my design on: