db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jdo Wiki] Update of "ScalableBackEnd" by RichardSchilling
Date Fri, 07 Dec 2007 07:09:24 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jdo Wiki" for change notification.

The following page has been changed by RichardSchilling:
http://wiki.apache.org/jdo/ScalableBackEnd

The comment on the change is:
added to the design approach and some background information.

------------------------------------------------------------------------------
  This page is for design of a scalable back end for a JDO front end using the JDO 1.0 Reference
Implementation front end as a starting point. This is in the svn repository in the fostore20
project.
  
- The FOStore back end uses Netbeans MDR repository, which is an open source key/value datastore
but has no query capability.  Another challenge in working with FOStore is the lack of readily
available documentation, and advanced features found in normal production grade databases,
like data store management tools.  FOStore is simply not intended to be used as a production
database.  But, the approach taken by FOStore is valid, and it would be very very useful to
have true object store written in Java that JDO can lay on top of.  The NIO API and other
features of Java that have improved performance of the Java VM make this a reasonable idea.
+ There are several challenges in JDO backend design that are illustrated by FOStore.  The
first is that FOStore back end uses Netbeans MDR repository, which is an open source key/value
datastore but has no query capability.  Another challenge in working with FOStore is the lack
of readily available documentation, and advanced features found in normal production grade
databases, like data store management tools.  FOStore is simply not intended to be used as
a production database.  
+ 
+ But, the design approach and feature set of FOStore is an important influence on this project,
and will serve us well.  To begin with, it will be very useful to have an object data store
written in Java that JDO can interface to.  Second the FOStore project provides some useful
design patterns.  On other fronts, the NIO API and other features of Java as of November 2007
have improved performance of the Java VM also make this project a reasonable idea.
+ 
+ 
+ == Design Approach ==
+ 
+ The development of the ScalableBackend will be done under the Agile development methodology.
 It is beyond the scope of this Wiki to explain Agile development methodology itself, so it
is strongly suggested you research Agile and familiarize yourself with it.
+ 
+ == Design Activities ==
+ 
+ As part of the design process the following activities will take place:
+ 
+  * a thourough review of the current and past literature on data base and data store design
  
  
  
+ == Key Features ==
  Here are some key design features that the end product will have:
  
   * written in Java
   * data store management and monitoring tools
   * a stabalized Java API useful for building clients that connect to the data store
  
- 

Mime
View raw message