Re: Looking for a lightweight persistance framwork
- From: charlesbos73 <cbossens73@xxxxxxxx>
- Date: Sun, 17 May 2009 14:44:07 -0700 (PDT)
On May 16, 6:37 pm, Roger <roger.var...@xxxxxxxxxxxxxx> wrote:
I'm about to start a small web project that's going to need a small database
comprising about half a dozen master data tables and two or three
transactional tables. The size of the project doesn't warrant a full blown
persistance framework like iBatis or Hibernate, and I really can't be arsed
to roll my own. So what would people recommend?
If the solution to your problem is really better expressed
using a relational DB *and* if you really need to use Java
then you have to deal with the "Object-Relational impedance
mismatch". In that case you'd be better to reuse one of
the tested and proven ORM out there, as others pointed out.
However, seen that it is a small web project and seen that
you happen to be posting in a newsgroup that talks about a
language that can be used in a OO way, it may be a good
opportunity to discover how simple and elegant an OODB can
be.
Note that this shall come as heresy in a newsgroup where
procedural advice on one hand, and RDB advice on the other,
are given daily as it was perfectly normal.
Some people like the XML + ORM flagellation coupled with
Java used in a purely procedural way (coupled with a
little GOTO-style programming here and there... But nothing
can go wrong when you know fineprint 6.3.2.17b of the JLS
right !? ;)
Other consider this kind of development to be everything
that is wrong with Java.
Ted Neward calls this kind of development the "Vietnam
war of software development". Englightening read.
So what would people recommend?
Reading Ted Newards's "Vietnam of sofware development"
IBM DeveloperWorks "The busy Java developer's guide to db4o"
articles by the same author.
db4o
Model your solution using OO techniques (once again, this
is probably heresy in this newsgroup) and use an OODB like
db4o.
A small web project is probably the perfect place
to start and the beauty of OO is that if it is done
correctly, changes becomes trivial later on.
I'm probably very lucky to work in a domain where OO
shines... Most developers here are so used to do
ORM plumbing in their dayjob that their mind became
hardwired to answer "use a SQL RDB".
Mindboggling.
.
- Follow-Ups:
- Re: Looking for a lightweight persistance framwork
- From: Arved Sandstrom
- Re: Looking for a lightweight persistance framwork
- From: Tom Anderson
- Re: Looking for a lightweight persistance framwork
- From: Lew
- Re: Looking for a lightweight persistance framwork
- References:
- Looking for a lightweight persistance framwork
- From: Roger
- Looking for a lightweight persistance framwork
- Prev by Date: Re: Nulling an object
- Next by Date: Re: Nulling an object
- Previous by thread: Re: Looking for a lightweight persistance framwork
- Next by thread: Re: Looking for a lightweight persistance framwork
- Index(es):
Relevant Pages
|