C# 7 and .NET Core 2.0 High Performance

The Dependency Inversion principle

The Dependency Inversion principle states that high-level modules should not depend on low-level modules and both of them should depend on abstractions.

The software application contains numerous types of dependencies. A dependency could be a framework dependency, a third-party libraries dependency, a web service dependency, a database dependency, a class dependency, and so on. As per the Dependency Inversion principle, the dependencies should not be tightly coupled with one another.

For example, in the layered architecture approach we have a presentation layer where all the views are defined; the service layer that exposes certain methods used by the presentation layer; the business layer that contains ...