Separated layers are one of the fundamental principles of software design. Your framework is just the topmost layer, and your business code should not depend on it. While we will touch a few package design basics, the focus is on how to actually DO it: Expose the user accounts in your model to your framework without depending on it. Separate form input validation from entities. Isolate ORM-specific code in bridges. We’ll also take a look at Deptrac, a tool that helps you to to visualize and stick to that separation during your project’s lifetime.


Comments are closed.

Kendra Jones at 11:03 on 4 May 2019

Great insights, great examples. Useful, implementable information.

Great talk thoroughly explaining the process of converting an application that depends on a framework to an application that is separated from the framework.

Roger Creasy at 11:11 on 4 May 2019

Good talk with a lot of information. Good code examples. Andreas is very knowledgeable on this topic. I found the value object explanation a little confusing. The talk moves quickly and covers a lot. He did a great job of fielding questions at the end of the talk.

Steve Grunwell at 11:12 on 4 May 2019

This is a talk that would have saved me weeks of work had I seen the talk even six months ago. A great, reasonable approach to structuring applications in a way that is both maintainable and testable.

I enjoy a good, technical talk like this one. Good depth and good Questions and Answers at the end.