Neeme Praks wrote:
> Hi all!
>
> I finally had a chance to take some time off and had a look at some of
> the SEDA papers on Matt's webpage. The concept sounded a bit similar to
> the project that we are doing with JMS&MDB (hosted by JBoss). So... I
> was wondering how do these two concepts compare?
>
> My initial "gut-feeling" is that JMS is more heavy-weight and SEDA is
> more light-weight... JMS has more "enterprise" features; meaning
> transactions, persistence, etc.
>
> As I know more of JMS than I know about SEDA, maybe more knowledgeable
> people (Berin?) can fill in here? Also, the features are probably very
> much up to specific implementations of SEDA, so, how do Sandstorm and
> Avalon compare to JMS (and to each-other) in this sense...?
>
> Rgds,
> Neeme
The big difference is in the granularity of the components. The underlying
concept is the same. However there are also some other things to consider:
* SEDA is at a lower level, meant to build servers (like Phoenix/Avalon)
* JMS is at a business level, meant to build applications
* SEDA can easily be dynamically rerouted at runtime
* JMS is usually for static solutions that work for a particular solution
If you are looking to solve *business* problems, I would go with JMS.
If you are looking to build a JMS server or some other highly scalable
server, look to SEDA.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
