Advice on persistent storage in Java
From: john martin (jmartin_at_cs.stanford.edu)
Date: 12/11/04
- Next message: Chris Parsons: "Re: Advice on persistent storage in Java"
- Previous message: Robert Klemme: "Re: federate several datasources"
- Next in thread: Chris Parsons: "Re: Advice on persistent storage in Java"
- Reply: Chris Parsons: "Re: Advice on persistent storage in Java"
- Reply: Luke Webber: "Re: Advice on persistent storage in Java"
- Reply: IchBin: "Re: Advice on persistent storage in Java"
- Reply: Manuel J. Goyenechea: "Re: Advice on persistent storage in Java"
- Reply: john martin: "Re: Advice on persistent storage in Java"
- Reply: frebe: "Re: Advice on persistent storage in Java"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 10 Dec 2004 21:14:04 -0600
I need some advice on persistent storage in Java. Basically, I'm writing
an application that I'd like to be in pure Java (including any backend
stuff it relies on, I'd like it to all run in the same VM). It has to
store a potentially large data structure. I'd like to have as little
hassle with SQL as possible, since I haven't done a ton of DB stuff,
though it seems that it may be necessary, and so I'm not totally averse
to using a regular SQL DB.
The two general options I'm considering are using an object oriented DB
(e.g., PERST, http://www.garret.ru/~knizhnik/perst.html), and a regular
SQL DB (e.g., hsqldb, http://hsqldb.sourceforge.net/).
Both PERST and hsqldb are pure Java, so that meets my first requirement
(basically, I don't want someone to have to install a seperate DB
product to run my app). I like the idea of using an OODB, but it's not
totally transparent, and I won't be doing the most complex SQL in the
world, so I'm not sure if it'll really save me any work. Has anyone had
experience with either of the above tools? Anyone have any general
advice for easily storing (possibly large) object oriented data
structures in a way that's rather efficient and fault tolerant (i.e.,
not a flat text or XML file) but not a complete pain in the ass to
implement?
Any advice from people who've either done object oriented DB stuff or
who've had to bundle basic DB capability in a Java application would be
much appreciated.
-john
- Next message: Chris Parsons: "Re: Advice on persistent storage in Java"
- Previous message: Robert Klemme: "Re: federate several datasources"
- Next in thread: Chris Parsons: "Re: Advice on persistent storage in Java"
- Reply: Chris Parsons: "Re: Advice on persistent storage in Java"
- Reply: Luke Webber: "Re: Advice on persistent storage in Java"
- Reply: IchBin: "Re: Advice on persistent storage in Java"
- Reply: Manuel J. Goyenechea: "Re: Advice on persistent storage in Java"
- Reply: john martin: "Re: Advice on persistent storage in Java"
- Reply: frebe: "Re: Advice on persistent storage in Java"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|