Stefan Wagner

«Truth can only be found in one place: the code.»  Robert C. Martin alias Uncle Bob


Blog | Archive | Resume | Projects | References

Independent Domain Model

09 Sep 2014 | architecture, maven

In our current project, we made a design decision for our domain model to be independent of any concrete persistence technology. Due to the fact that the persistence layer had to be replaceable in order to fit in any client environment, we came to the conclusion that we needed to define an API module for the persistence and a temporary or default implementation of it.

independent domain model

The domain model is overall available, each module depends on it. Besides of representing the domain, it also acts as a data transfer object. The implementation of the persistence is capsuled behind a module of interfaces.

This structure has a major disadvantage: we lose all the comfort of JPA. Lazy loading, gone! We have to send all the associated data to the consumer.

comments powered by Disqus

Older · View Archive (11)

Wiki History Book

As per a request of Professor Dr. Peter Gloor of the Massachusetts Institute of Technology, MIT, Center for Collective Intelligence I’ve worked out three different versions of a graph representation on the connections among famous people of English Wikipedia. Each person was represented by a node. More people referred to a person, thicker got its node.

Newer

Jobseeking with OWL

In the current CTI science project, we’re testing OWL and the possibility to classify objects as well. The idea is to find the right candidat, a job seeker, for a certain vacancy.