Speedo, what is it?
Speedo is an open source implementation of the
JDO (TM) 2.0 specification
and the EJB 3.0
specification. It is hosted by ObjectWeb.
Speedo main benefits
- Possible choice of optimistic or pessimistic transaction mode
- Cache of persistent objects, with a choice of several replacement
policies (LRU | MRU | FIFO | ...)
- Data prefetching at query evaluation time or collection loading:
later accesses to objects will not require any I/O to the
data store
- Management of relation ships (coherency management)
- Detach / Attach feature
- Able to create the SQL schema
- Various identifier support (application (composite or single),
SQL sequence, speedo)
- Lot of types supported
- Lot of
databases supported (Oracle, MS SQL server, Mysql, Postgres, ...)
- Through JORM and MEDOR, access to legacy relational databases, as
well as any other data store supported by JORM and MEDOR
Speedo reuses several ObjectWeb frameworks:
- JORM, a framework for
mapping objects onto persistent supports such as relational
databases.
- MEDOR, a query framework
permitting queries over distributed data sources.
- Perseus is a persistence framework managing several
aspects such as caching, pooling, and concurrency control.
- Fractal, the ObjectWeb
component model used to build middleware components and frameworks.
- Julia, Fractal's
reference implementation.
- ASM, a framework to manage Java
byte code.
- Monolog, an API of
logging which aims at being independant from the logging system
(log4j, jdk1.4).
Back to the Speedo documentation