Without a dominant proprietary solution and with EJB in disarray, the software industry has a significant vacuum in the Java persistence solution market. Many are looking to the next best standard. With the Java Data Objects (JDO) 2.0 specification under way, the timing is right for JDO to seize this opportunity.
by Bruce Tate
March 11, 2004
uring the past decade, I've witnessed remarkable change in the software industry's overall approach to persistence. Though measuring Plain Old Java Object (POJO) solutions in terms of market share is tough, I've noticed a recent resurgence of JDBC programming. Some developers now roll their own JDBC solutions, while others look to increasingly robust JDBC frameworks. These frameworks allow some abstraction and provide better control over SQL, which can be important for performance, and automated frameworks can support a popular design pattern called data access object (DAO).
I think this trend is in part a response to the existing persistence alternatives. In the past, persistence frameworks often burned developers for many reasons, including the following:
EJB container-managed persistence (CMP) still has serious technical limitations.
Object-oriented databases never accumulated enough market share to take root.
Many persistence frameworks could not provide adequate performance.
Some proprietary frameworks failed, leaving their customers in the lurch.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
uring the past decade, I've witnessed remarkable change in the software industry's overall approach to persistence. Though measuring Plain Old Java Object (POJO) solutions in terms of market share is tough, I've noticed a recent resurgence of JDBC programming. Some developers now roll their own JDBC solutions, while others look to increasingly robust JDBC frameworks. These frameworks allow some abstraction and provide better control over SQL, which can be important for performance, and automated frameworks can support a popular design pattern called data access object (DAO).
