When to Use Which Mapping Strategy?

This is the million-dollar question.

The answer is the usual, dissatisfying, “it depends”.

No hard-and-fast rule

Since each mapping strategy has different advantages and disadvantages, we should resist the urge to define a single strategy as a hard-and-fast global rule for the whole codebase. This goes against our instincts, as it feels untidy to mix patterns within the same codebase. But knowingly choosing a pattern that is not the best pattern for a certain job just to serve our sense of tidiness is simply irresponsible.

Software evolution

Also, as software evolves over time, the ...