Week 10: S.O.L.I.D. Part 2, Persistence, Hexagonal architecture

In this lecture, we look at the remaining principles of S.O.L.I.D: the Liskov Substitution Principle, the Interface Segregation Principle, and Dependency Inversion Principle (DIP). We see how DIP can be applied to give the Library Application as layer to handle persistency. Then we are going to revisit layered architecture and introduce Hexagonal Architecture.

Slides
References:
- Robert C. Martin: "The Principles of OOD". The first 5 principles are the S.O.L.I.D. principles
- The article by Alistair Cockburn introducing Hexagonal Architecture / Port and Adapter Pattern
- A JPA Tutorial using Eclipselink as JPA implementation and Derby as database
- A JPA Tutorial from Oracle
If you use persistence in your exam project, make sure it is an embedded database and does not use a database server. The embedded database does not require me to setup any databae servers when I want to run your project. Also, the embeded database is a file or directory that should be part of your Eclipse project, which you then can send me. In my example, I am using Sqlite, which I recommend, but Derby as embedded database is also an option. The META-INF/persistence.xml file in the example Library Application shows how to set up Sqlite.
Programming examples as Eclipse projects
- An updated version of the library application with user interface and persistence layer.

On to Week 9: Observer Pattern, MVC, Presentation Layer, S.O.L.I.D. Part of Lecture Plan

Hubert Baumeister

April 23, 2018