What is hexagonal architecture? In short and simple, it is a way of coding your application without being dependent on any external libraries or frameworks. All application specific logic should be contained an not be tightly coupled. By defining interfaces at the boundaries of your application, you will allow external libraries to implement functionality hidden within your actual application. Confused? Read along!
This entry was originally posted at http://sjoerdjob.com/ In a recent message to the Django mailing list, a remark was placed that the URL routing of Django was tightly coupled to the Django core. From what I understood of the requirements placed on the routing, I found it a weird statement. I decided to investigate.
The fourth part in the series on the SOLID principles based on the meetup we did a few weeks ago, this blog post describes the Liskov Substitution Principle.
The third part of the series on the SOLID principles, based on the technight on the same subject.
The second of the seven part series on the SOLID principles, this blog describes the first of the principles, the Single Responsibility Principle (SRP).
A few weeks ago, I gave a presentation about the SOLID principles, which was quite popular. In fact, it was so popular that we had to close the RSVP on meetup a few days in advance, due to a lack of space. For future reference, we are working on streaming solutions for our technights, but this was not yet in place back then. For that reason, I decided to dedicate a 7-part blog to the principles, starting with the why of the SOLID principles.