Get Your Hands Dirty on Clean Architecture - Second Edition

9

Mapping between Boundaries

In the previous chapters, we’ve discussed the web, application, domain, and persistence layers and what each of those layers contributes to implementing a use case.

We have, however, barely touched on the dreaded and omnipresent topic of mapping between the models of each layer. I bet you’ve had a discussion at some point about whether to use the same model in two layers in order to avoid implementing a mapper.

The argument might have gone something like this:

Pro-mapping developer:

“If we don’t map between layers, we have to use the same model in both layers, which means that the layers will be tightly coupled!”

Contra-mapping developer:

“But if we do map between layers, we produce a lot of boilerplate code, which ...