Re: [ajug-members]: DB abstraction summary?

[Angus Berry <angus.berry@elken.com>]

I think we're on the same sheet of paper regarding 'scalability', I'll
forward you the emails I got from OJB folks regarding JDO, so you can be
sure.

Regarding Hibernate & JDO, I found some ng postings on google or
groups.google.com, from late 2003 by Christian, that were discouraging
about JDO & Hibernate in the short term, but they were prior to JBoss's
involvement, so the landscape may have changed. I can't really comment
about Hibernate otherwise, as I haven't recently pushed it very far. May
some else can illuminate about Hibernate & JDO.

For me Patrick Linskey summed up a key benefit of JDO (you'd have to
check the audio file for the exact quote), in that it allows you to
'defer decisions' until deployment, which is true even now with OJB-JDO.
You could theoretically code right now against JDO on OJB and get to
production time and pick another JDO compliant implementation to suit
your needs. I know his product had some great features that are beyond
my current requirements, but the ability simply swap out the persistence
layer for new back end features like failover, would be music to most
project stakeholder's ears.

I'll shoot you those emails now.

On Tue, 2004-05-04 at 18:20, John Wells wrote:
> Angus Berry said:
> > I hope I wasn't accidentally creating any FUD around OJB... the JDO
> > reference implementation doesn't scale and also Licensing could be murky
> > water since they graft on Sun's work.
> 
> Angus,
> 
> I'm still a bit hazy on what you mean.  Scalability means to me that you
> can accomodate increased application load with additional resources...are
> you saying that the JDO reference implementation doesn't perform well as
> your application data size grows?
> 
> How does Hibernate compare, out of curiosity?
> 
> Thanks,
> John
> 
> 
> 0