Content

Over the past fifteen years, typical architecture has shifted from one extreme to the other. Where business logic and SQL statements used to be buried behind click events in the user interface, today we find clean layer architectures. The theoretical “pattern implementation” of such a layer architecture usually involves the use of an MV* interface pattern. Added to this are a business layer, a repository, and an O/R mapper. In practice, however, the implementation of such an architecture often leads to anemic domain object models, empty business layers, and repositories that far exceed their actual purpose. In this session, I would like to critically examine this approach together with you. I will also use a small sample project to show you alternative solutions and encourage you to try out new ideas so that you can write leaner, more maintainable software with less effort in the future.