Practical Rich Domain Models
Many developers are interested in using Rich Domain Models in their applications because they provide an enormous value for
relatively little work. Rich Domain Models are easy to test, easy to extend and easy to work with. However, they are also one of the least understood ways of developing an application because they are organic. There's no definitive guide to Rich Domain Models, nor will there ever be one. There are some do's and don'ts but much remains unwritten and much depends on your specific needs and objectives. The number one rule is: "keep things as simple as possible". Other rules are: "test first, implement later", "persist only what you need, and nothing more", "build the process as you understand it", "talk to your users as much as possible and in their language". Rich Domain Models require an attitude where it's possible to throw things overboard halfway through a project to improve the design and the application. It also requires you to do the most obvious and sensible thing.
This session will discuss a real-world Rich Domain Model and how transaction management, security and persistence are affected. The persistence tool of choice is Hibernate 3.1. The goal is to have a very sensible application design that pushes persistence (and thus transaction management) into a corner so that your mind is freed to think about three things: the user interface, the business logic and the database.
During this session the audience will learn how to implement this specific application and understand the philosophies that have been applied.
Audience
Beginner
Speaker
