Domain-Driven Design Community

Problem: When a new system is being built that must
have a large interface with another, the difficulty of relating the two
models can eventually overwhelm the intent of the new model altogether,
causing it to be modified to resemble the other system?s model, in an
ad hoc fashion. The models of legacy systems are usually weak, and even
the exception that is well developed may not fit the needs of the
current project. Yet there may be a lot of value in the integration,
and sometimes it is an absolute requirement.

Solution:
Create an isolating layer to provide clients with functionality in
terms of their own domain model. The layer talks to the other system
through its existing interface, requiring little or no modification to
the other system. Internally, the layer translates in both directions
as necessary between the two models.