title: N-Layer to Hexagonal (Ports and Adapters) architecture
body: <p>Alistair Cockburn introduced a Hexagonal architecture, now it is called <a href="http://alistair.cockburn.us/Hexagonal+architecture">Ports and Adapters</a> pattern. In my understanding, the concept is similar to n-layer architecture where one layer depends on the other layer via abstraction (interface) only. For example, the application layer depends on the many repository services interfaces rather it's implementation. There is no need of a separate implementation of a ports or adapters here. An IoC container like Unity can inject the implementation of the repositories, so adapters are not necessary.</p>
  
  <p>Am I confusing this ports and adapters pattern with DIP (Dependency Injection Principle)?</p>
  
  <p>Can someone point me to an implementation of the ports and adapters pattern? Thanks.</p>