Layered Architecture, Dependency Injection, and Dependency Inversion
Building loosely coupled application architectures requires more than just separating your application into different layers.
by Jean-Paul S. Boodhoo
June 18, 2007
ost developers understand the value of the layered approach to architecture. The main principle behind layered architectures is that of "separation of responsibility". Each layer is responsible for a finite amount of work. Any work that cannot (read should not) be done by a particular layer gets delegated to a layer more appropriate for handling the task.
Unfortunately, people using layered architectures can often run into a scenario where they introduce an unnecessary amount of coupling between layers of their application. A high degree of coupling is one factor that can lead to fragile application architectures that are difficult to change or extend.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
ost developers understand the value of the layered approach to architecture. The main principle behind layered architectures is that of "separation of responsibility". Each layer is responsible for a finite amount of work. Any work that cannot (read should not) be done by a particular layer gets delegated to a layer more appropriate for handling the task.
