Hi all,
Can anybody share their experiences in deploying a design solution
that involves an ODBMS. Are there any major pitfalls in using a ODBMS to
persist your objects as opposed to using a relational database. I'm not
trying to completely avoid a relational database, but I need a odbms that
could co-exist with a rdbms and take care of persisting my objects.
I'm right now evaluating some ODBMS products, which will provide
simple means for storage and fast retrieval of my objects in a distributed,
multi-user environment. Support for retrieving data using complex queries is
an absolute necessity.
My goal is to avoid all the middleware components(O-R Tools)
that's needed to keep my objects persistent. Hopefully, I'd also avoid
further bloat of my application without any use of Entity Beans. I'm sure my
application would end up with 40% less code. I've been also hearing that in
certain cases the applications using odbms products are 10 times faster than
the ones using rdbms. Seems like the cost benefits of using an ODBMS product
is extremely good as they are a lot cheaper than the existing RDBMS
products.
Anyway, my bottom line is, I'm looking for a solution to persist
my objects and retrieve them fast. I don't need anything fancy at all that
today's RDBMS products provide. Any pointers/tips/warnings from architects &
developers will help me out a lot.
Winston.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
