JDO 2.0: Another shot at transparent persistence

Java Data Objects offers a standard model for transparent persistence (or close to it). The 2.0 version of the specification has given us many new features. For one, it attacks the OR view, with a standard OR mapping schema. It has also learnt from other practical issues that have come out of the use of JDO 1.x. Now you are not locked into JDO-QL (which has been improved), and bytecode twiddling isn't required anymore. This talk discusses what JDO is, and isn't; what JDO 2.0 is all about, and how it can help you scale out your data tier.

Java Data Objects offers a standard model for transparent persistence (or close to it). The 2.0 version of the specification has given us many new features. For one, it attacks the OR view, with a standard OR mapping schema. It has also learnt from other practical issues that have come out of the use of JDO 1.x. Now you are not locked into JDO-QL (which has been improved), and bytecode twiddling isn't required anymore. This talk discusses what JDO is, and isn't; what JDO 2.0 is all about, and how it can help you scale out your data tier.

About Dion Almaer

Dion Almaer is the founder and CTO of Adigio, Inc. He is an architect, mentor, pragmatic, and evangelist of technologies such as J2EE, JDO, AOP, and Groovy. He is the Editor-in-Chief of TheServerSide.com J2EE Community and enjoys working in the community. He is a member of the Java Community Process, where he participates on various expert groups.

More About Dion »