Skip to Main Content
Get Your Hands Dirty on Clean Architecture
book

Get Your Hands Dirty on Clean Architecture

by Tom Hombergs
September 2019
Beginner content levelBeginner
156 pages
2h 47m
English
Packt Publishing
Content preview from Get Your Hands Dirty on Clean Architecture

Chapter 8

Mapping Between Boundaries

In the previous chapters, we 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 upon the dreaded and omnipresent topic of mapping between the models of each layer. I bet you have 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 ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Get Your Hands Dirty on Clean Architecture - Second Edition

Get Your Hands Dirty on Clean Architecture - Second Edition

Tom Hombergs

Publisher Resources

ISBN: 9781839211966Other