My understanding is that you are right - the ODBMS market is still
pretty immature and their products don't offer the performance or
scalability that exists in the RDBMS market.

Then there are ORDBMS ideas - blending the two concepts - but that
hasn't really caught on either...

From an OO development perspective (al la CSLA) we have the same problem
with an ODBMS as with an RDBMS - the data must be mapped from the
database constructs into our objects.

What we _really_ need is an ODBMS (or maybe ORDBMS) that allows our
actual .NET business objects to move directly into and out of the data
store. Now _that_ would be cool, because it would eliminate the mapping
layer entirely (or at least push it all the way down into the storage
layer itself).

Rocky

> -----Original Message-----
> From: Jeffrey Price [mailto:jeff@t...] 
> Sent: Tuesday, March 04, 2003 6:59 PM
> To: expert_vb_business_objects
> Subject: [expert_vb_business_objects] Object Persistence & 
> "Object Databases"
> 
> 
> I've been reading a lot lately about "post-relational" or "object 
> databases" such as Cache' (www.cachedatabase.com) or Prevayler 
> (sourceforge.net/projects/prevayler).
> 
> It seems that these systems would lack the robustness of "mature" 
> database servers such as MSSQL or Oracle, but are there other 
> benefits/pitfalls? 
> 
> Such articles have certainly peaked my curiosity. Has anyone 
> out there 
> had any experience with these or similar systems (especially in 
> conjunction with the CSLA methodology)?
> 
>