Java based message passing system

[chris]

Hi,

I need to exchange messages between machines connected by a 1000MBit
Ethernet. I will probably need to exchange between 30 and 100 messages
per second in both directions. The typical message will probably be 1kB,
messages bigger than 4kB should be rare (most of it basic datatypes like
double).

Is that possible with Java? Should the message passing system be RMI
based, or would you recommend something else? How does such a solution
scale (if I have one machine exchanging messages with a couple of other
machines)?

Is it even possible to realize a scenario like this with Jini and
JavaSpaces?

Thanks for your opinion,
Chris

 

[Jim Sculley]

Hi,

I need to exchange messages between machines connected by a 1000MBit
Ethernet. I will probably need to exchange between 30 and 100 messages
per second in both directions. The typical message will probably be 1kB,
messages bigger than 4kB should be rare (most of it basic datatypes like
double).

Is that possible with Java? Should the message passing system be RMI
based, or would you recommend something else? How does such a solution
scale (if I have one machine exchanging messages with a couple of other
machines)?

http://java.sun.com/products/jms/


Jim S.

 

[Jose Rubio]

Hi,

I need to exchange messages between machines connected by a 1000MBit
Ethernet. I will probably need to exchange between 30 and 100 messages
per second in both directions. The typical message will probably be 1kB,
messages bigger than 4kB should be rare (most of it basic datatypes like
double).

Is that possible with Java? Should the message passing system be RMI
based, or would you recommend something else? How does such a solution
scale (if I have one machine exchanging messages with a couple of other
machines)?

Is it even possible to realize a scenario like this with Jini and
JavaSpaces?

Thanks for your opinion,
Chris

Take a look at JMS.

http://java.sun.com/products/jms/

You could also implement your own protocol and use sockets. But you mention
exchanging messages between multiple machines, so JMS would be better suited
since it's already done for you. The decision will be based on your
architecture, not the load.