EJBs can be ACID-compliant.. the key is you don't write new values to the
beans.
If a value needs to be updated, you write to the database and then kill
and remake the bean. This way you're keeping the database as your sole
data abstraction, and the beans are just a local mirror of some parts.
So if reading DB values much more than writing, you might want to consider
them. If it's a 3:1 ratio then you're just creating a headache for
yourself. For a site with 10,000 hits a second that call DB values that
are changed once a month.. you probably want to keep a web server-RAM
mirror of the data.
EJBs are of course one solution, photo.net uses a similar TCL-based idea
for their drop down menus, I believe, and it works well for
them. Similar TCL-based ideas have worked well for me. Maybe it just
comes down to wanting to sail in more mainstream waters (easier to
find new programmers with experience, wanting to add your project to
their resume, lots of good books as resources). My personal concern for
reducing the load on my database is low on my priority list compared to
those other things.. -T
On Wed, 2 May 2001, Jerry Asher wrote:
> At 08:48 PM 5/1/01 -0400, you wrote:
> >On 2001.05.01, Tim Darling <[EMAIL PROTECTED]> wrote:
> > > Further Enterprise Java Beans make websites that are
> > > much faster because a DB call isn't made every time a user hits a
> > > page. DB calls are 1,000 - 10,000 times slower than a call to a java bean
> > > which is acting as an abstraction of the database.
> >
> >I can implement the equivalent of Java beans using two or three
> >procs that act as wrappers around an nsv_* interface, all in
> >Tcl and AOLserver API.
>
> I'm with both Tim and Dossy here. There's a bit market for EJBs and
> there's a lot that can be done in AOLserver itself.
>
> I am curious: how do EJB's handle the ACID test? Is the performance
> penalty a reasonable cost for those portions of your project that have ACID
> requirements? Is the EJB/DB architecture more akin to a AOLserver as
> application server/DB solution than the typical AOLserver as web server/DB
> solution described so well in WTR? If so, does what can we learn/steal
> from EJBs to make the AOLserver environment more productive, more
> efficient, more powerful, or just more compatible?
>
> Jerry
> =====================================================
> Jerry Asher [EMAIL PROTECTED]
> 1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980
> Berkeley, CA 94709 Fax: (877) 311-8688
>
