• Post Reply Bookmark Topic Watch Topic
  • New Topic

JMS for 2 way communication

 
Abdul Aleem
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

This is a design issue, our requirement is swing client submit trading
info to trading server
(located at multiple broker's office remotely ) and trading server has to update swing clients with trade updates.

Key issue is that both actions takes place asynchronoulsy

Hence we decided to rely on JMS


Is it a good design to have p2p and pub/sub implementation on both client
and server ??

I would greatly appreciate any suggestions / comments or even if JMS is not an appropriate choice?? use XML based approach ??

Many thankss,
Abdul
 
Abdul Aleem
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
Just thought if the question was not clear enough, I would
appreciate if any thought on any of the points below


I have a swing client which need to communicate ( both send and
receive message ) from a distributed system.

Here are my queries.

a) both send and receive is asynchronous - is it a good design to
have two set of queues on acting as a requestQueue and other
as responseQueue

b) we need persisting messages meaning crash recovery, our design is more complicated that each swing client will need to listen to more
than 100 requestQueue & responseQueues - because the client n eeds to communicate with 100's of broker offices located remotely to place orders as well as receive trade updates

c) Finally might sound a silly question,
If we have a requestQueue and responseQueue (point a) , can
the same responseQueue be used for Synchronous and Asynhronous communication ?? I mean the swing client need to query
some user specific data (just a request response) will be wise to make use of existing channel instead of creating one ? any thoughts ??


d) Any inputs on scalability of this system, will it scale very well ??
Highly appreciate any thoughts or even if you find some flaw in the approach kindly let me know.


I appreciate if someone could throw some light, as we are a very small team (2) with limited expertise on JMS.


Many thanks,
Abdul
 
Gabriel Buheler
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It seems fine to use JMS architecture.

I am assuming your system is going to be implemented within an intranet.

Regarding scability, it will offered by the EJB container when implement your MDB's. There are more options after a good design/architecture to do it more scalable.

Adding resources to your system, or clustering.

I will recommend publish-subscribe, with durable configuration.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!