Randy,
I'm sure you figured this out on your own, but feel I have to comment.
Obviously your needs for parallel processing require a different
architecture than is provided by EJB. EJB and Microsoft's MTS are both
Component Transaction Monitors (CTMs), which are build around synchronous
messaging systems. You are in need, IMHO, of an asynchronous system, which
is a completely different architecture.
The system you built sounds like it provides excellent throughput and is
probably very scalable. While I'm strong supporter of EJB, I believe every
technology has its place. In this case, EJB is not a good fit.
Good luck!
Richard
-----Original Message-----
From: Mcree, Randy
To: [EMAIL PROTECTED]
Sent: 3/12/99 10:49 AM
Subject: Re: Modeling an application with parallelism using EJB (reply)
> Sounds like the RDBMS does all the hard work anyway.
Actually, no. That is part of the problem, a single SQL query, no matter
how
complex, only involves one cpu. That cpu can touch as many discs as
necessary, but the single cpu limits the speed. So this application
tries to
get as many SQL queries going as possible, up to some tuning limit which
depends on the optimal number of simultaneous SQL queries per cpu.
(Typically talking sixteen or more cpus and a room full of discs)
As a middleware developer I would like the customer to be able to write
a
straightforward EJB application and then get it to scale to this size
system...
Randy McRee
===========================================================================
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".
