August 2018
Intermediate to advanced
372 pages
9h 29m
English
It is now time to define the dependency inversion principle:
Modules should depend on abstractions rather than on concrete implementations.
Abstractions represent the high-level details of a module, and the interaction among modules should be done at this level. Low-level details are volatile and ever-evolving. We previously stated that there are no problems with evolved modules, but of course, we don't want to break module interactions because of low-level details, and an excellent way to do this is to use abstractions rather than concrete implementations. The following questions will help you identify how well you are doing:
As discussed earlier in this ...
Read now
Unlock full access