Repository pattern

The basic idea of the repository pattern is to seperate buisness logic and persistence logic through a list like sematic.

The great thing about this, as asposded to the way orm’s does things is that you force the developer to think about when and how do i access data.You just can’t navigate around in the model, and expect some framework to handle it magiccally for you.

The idea of a repository teams up well with aggregates. Imagine the repository as an interface of List[Aggregate], where you can add, remove, delete etc. from.

#Logging

I was browsing through our code at Schantz were i do my daytime hacking. I found something that’s not unusual in our code base. To be fair it’s not unusual in most codebases.

The issue is logging, and more specific what log level should be used when.

So i’ve decided to give you my take on it.

Error

The error statement should only be used for actual errors. So if the system will fail catastrophically, and there is no known way to recover, a error is written.