Several tools simplify the task of adding database persistence to an application, but this requirement often complicates a developer's life more than it should. Some even question whether developers should be creating persistent applications without the help of database experts. Others promote additional layers of technology that automate the persistence mapping to a level where it is irrelevant. Most developers silently accept that their data must eventually map to a relational model.

However, increasingly the heretics among us ask is this always the optimum solution?

Architects, database administrators, software development managers and developers all need to reach a consensus on persistence strategy for their project. Failure to reach this consensus can result in the project running late, the application not scaling, and escalating maintenance costs.

Join us at this session to get an overview of persistence options and in a live demo discover an innovative new one. We explore the results when your get you persistence wrong and the benefits of getting it right. You will gain a richer understanding of Java application persistence, and will be ready to make your Java applications more valuable.