Message Routing Paradigms

Eric Newhuis <>
Fri Dec 13 15:15:07 CET 2002


I am aware of Erlang's messaging capabilities and yet there is still a
general need for higher level protocols like the one's I mentioned.

Even the CosEvent module demonstrates acceptance of the decoupled
publish/subscribe paradigm.

Do you or anyone else have any idea of messaging "middleware" developed
with Erlang for Erlang that addresses message routing like the CosEvent
module, but without the overhead of CORBA?

Sincerely,
Eric
 


-----Original Message-----
From: 
[mailto:] On Behalf Of Sean Hinde
Sent: Friday, December 13, 2002 4:31 AM
To: 'Eric Newhuis'; 
Subject: RE: Message Routing Paradigms


Eric,
 
I'm not sure there is really a need for a paradigm - it is the basis of
Erlang.
 
To get 10k per second you are probably not wanting to do a lot of
processing on each message - but a simple round robin load balancer
based on differently tagged messages is probably no more than a single
gen_server with a little logic
 
I'm not familiar with these different mechanisms but my guess is that
they are only needed because they don't have Erlang :-)
 
Sean

-----Original Message-----
From: Eric Newhuis [mailto:]
Sent: 13 December 2002 04:07
To: 
Subject: Message Routing Paradigms


To whomever knows,
 
Are there any good information sources regarding Erlang message routing
paradigms?
 
I am interested in decoupling publishers and subscribers, possible
space-based load-balancing (like Java Spaces or IBM T-spaces),
content-based subject routing, and it must handle on order of 10K
messages per second per 1GHz CPU.
 

Sincerely,
Eric Newhuis
 
 




NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have
received this email in error please notify the sender immediately and
delete this email from your system without copying or disseminating it
or placing any reliance upon its contents.  We cannot accept liability
for any breaches of confidence arising through use of email.  Any
opinions expressed in this email (including attachments) are those of
the author and do not necessarily reflect our opinions.  We will not
accept responsibility for any commitments made by our employees outside
the scope of our business.  We do not warrant the accuracy or
completeness of such information.



More information about the erlang-questions mailing list