[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: *URGENT* -- Call for support
Hi James,
although this is a very interesting post I didn't find the time to respond
earlier, sorry. I will just comment one particular sentence of your post. see
below.
[snip]
>
> > * I'm quite convinced that ODBMS market is having a new birthday owing to
> > Java and J2EE
> > * EJB market is a huge potential for ODBMS
>
> They are really two different solutions to two different problems. EJBs
> pertain to managing resources in a scalable manner and abstracting business
> logic from the application. ODBMSs simply provide a persistent object
> store.
I disagree. This is not true for Java DBs. ozone in fact _is_ an application
server! Yes guys, I'm not megalomaniac or something. The code to actually store
objects does not make 10% of the entire code base!!! Moreover, I never did
focus on that part of ozone (therefore it's by comparison still very simple;).
I always focused on the performance and features of the "object runtime
environment" - fast method calls, object cache, transactions, etc. No matter
what they say, basically EJB provides a transactional, persistent runtime
environment for (business) objects. But this is in fact exactly what ozone does
and what it was made for.
This missunderstanding is a huge problem for ozone. People see that ozone is an
(OO) "database", well now they expect "database" behaviour. But the proxies and
the entire ozone programming model does not really fit into this picture.
Obviously this makes it hard for newbies to get familiar with ozone.
I would really like to hear your opinions on that. How do you picture the
future of ozone? What are the advantages/disadvantages compared to EJB and
JDO and other solutions? Are there any anyway? Or should we just switch to EJB?
Or am I completely wrong?...
Falko
--
______________________________________________________________________
Falko Braeutigam mailto:falko@smb-tec.com
SMB GmbH http://www.smb-tec.com