The Compile Log
Articles

JDO Genie Explained: Java Persistence for Relational Data

JDO Genie was a JDO 1.0 implementation for relational databases with distributed PersistenceManagers and per-developer licensing.

Elliot Marsh4′

§

JDO Genie was a high-performance implementation of the Java Data Objects specification for relational databases, and it shipped when object persistence choices still divided Java teams. The verdict from the surviving documented record is that JDO Genie qualified as a complete and practical option for its specification generation, with distributed deployment and developer licensing as its practical edges. The C2 Wiki, last edited June 27, 2014, describes it with the words “high performance Java Data Objects (JDO) implementation for relational databases”.

JDO Genie Mapped Java Objects to Relational Tables

JDO Genie mapped Java objects to relational tables through object-relational mapping and shipped with the standalone JDO Genie Workbench IDE. The 2003 Core Java Data Objects survey via Flylib records the mapping approach and the Workbench. Hemisphere Technologies appears in the same survey as a professional-services firm centered on Java application development and deployment, a useful anchor for readers comparing vendor-backed tooling against community projects in Tutorials. The design targeted managed and unmanaged environments with leading relational databases as storage.

Which Relational Databases Did JDO Genie Support?

JDO Genie supported a broad roster of relational datastores current in the early-2000s survey window.

The roster below reflects the 2003 survey via Flylib. Version numbers appear only where the survey named them.

Datastore Version noted in the survey
Oracle No version stated
Microsoft SQL Server No version stated
Pointbase No version stated
SAP DB 7.3
Informix 9
Sybase No version stated
Interbase 6
Postgres 7.3.1
Firebird 1.0.2
MySQL 3.23.49 and 4.0.12

Oracle’s JDO overview, accessed November 16, 2026, adds that applications written to the JDO API stay independent of the underlying database. Teams that standardized one datastore still needed disciplined sequencing for schema-facing work, a concern familiar to planners using Feature Driven Development.

Distributed PersistenceManagers Removed a Serialization Step

JDO Genie allowed PersistenceManagers to run outside the server virtual machine, removing the need to serialize large graphs of connected value objects between clients and the server. The C2 Wiki description carries that design point. The 2003 survey adds remote access from a PersistenceManager in a client virtual machine to a Genie server virtual machine.

The surviving description phrases the second half as “PMs do not have to be in the same VM”, per the C2 Wiki record last edited June 27, 2014. Distributed layouts still fail in specific ways, and writing those failures down belongs in Lessons Learned.

What Did JDO Genie Cost Relative to Contemporary JDO Products?

JDO Genie listed below several rival JDO products at the developer-license level, with no runtime charge noted.

All figures in this section come from the 2003 survey via Flylib, stated per developer.

Product Edition Price in dollars
JDO Genie Professional 500
JDO Genie Enterprise 2000
Exadel JDO Standard 999
Exadel JDO Advanced 1499
Exadel JDO Enterprise 2999
Solarmetric Kodo Standard 600
Solarmetric Kodo Enterprise 3000

The survey notes no runtime costs for JDO Genie and no runtime royalties for either Kodo edition.

JDO Genie FAQ

What specification does JDO Genie implement?

JDO Genie implemented the Java Data Objects 1.0 specification with all required features and most optional features of that version. The C2 Wiki, last edited June 27, 2014, records that coverage. The JDO 1.0 standard was defined as JSR 12 under the Java Community Process, according to Oracle’s JDO overview accessed November 16, 2026.

Which company built JDO Genie?

Hemisphere Technologies built JDO Genie as a professional-services firm centered on Java application development and deployment. The 2003 Core Java Data Objects survey via Flylib gives that background. The same survey lists JDO Genie 1.3.2 with the standalone JDO Genie Workbench IDE and remote PersistenceManager access.

How does JDO Genie relate to later Java persistence standards?

JDO Genie belongs to the JDO 1 era; later standards moved through JDO 2.0 under JSR 243 to maintenance at Apache. Wikipedia, accessed November 16, 2026, dates JDO 2.0 to May 10, 2006. The same source dates JDO 2.2 to October 2008 and JDO 3.0 to April 2010. Apache stewardship began in 2005, according to the Apache JDO overview accessed November 16, 2026.

Is JDO Genie the same kind of standard as JPA?

JDO Genie is not the same kind of standard as JPA, which targets relational datastores while JDO covers datastore-agnostic transparent persistence. Wikipedia, accessed November 16, 2026, gives that distinction. The same source notes that vendor enhancers modify compiled class files so ordinary Java classes persist transparently.

#JDO Genie #Java Data Objects #Object-Relational Mapping #Java Persistence

Elliot Marsh

A veteran software developer with over a decade of experience building Java systems and guiding small development teams through agile projects.

Published November 16, 2026

Related articles

  1. Feature Driven Development: Five Steps That Ship Software

    Feature driven development runs software projects through five processes, shipping each client-valued feature in 2 to 10 days.