Analysis of a successful JDO case

Source: Internet
Author: User


Analysis of a successful JDO case

Source: link on jdocentral.com:
"A Case Study: replacing the persistence layer of a Business Process Engine with JDO"

This PDF describes the application development situation of a software application company in Massachusetts before and after JDO, initially, they developed a set of standardized Java Data Object layers that implement the odmg3.0 specification.

The data structure of their project is about 33 data classes, with hundreds of fields and some additional data tables (about 300). The scale is relatively large.

After using JDO, they found that the number, performance, and maintainability of the code they wrote for several years were not comparable to that of JDO (they used kodojdo2.4.2 ). For example, the performance data comparison: JDO: Self-writing bottom layer = 1842: 401, the gap is so big! For more details, please download this document.

This article includes the process of migrating from the bottom layer of Self-written JDBC to JDO, as well as performance comparison data of some development processes and times and different development modes (JDBC, JDO, and EJB.

The following are the original statements in the attached document:
The original article shows that JDO is more efficient than the self-written data packaging layer:
JDO is probably a far more productive environment than any home-grown persistence layer.

Another original article describes the loss of SQL performance to a certain extent:
It certainly wowould have yielded faster results if we had hand-coded the SQL for each class. but with 33 classes in the process engine, and roughly another 300 in the remainder of our application, a hard-coded approach does not seem like the best approach to take.

There is also a description of the situation in which JDO can be used to replace EJB:
With the availability of JDO, it makes you wonder when and if you wowould ever need an EJB container at all within your application architecture if you use it only as a front-end to your database.

The copyright in this article belongs to the author, but you are welcome to repost it on the premise that the source and original author are indicated. In additionMy columnView my other articles and provide valuable comments!

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.