Hi, I don't have practical experience with what you are suggesting, but are you sure javaspaces/jini is not a more appropriate framework for your system? thanks david jencks On 2001.05.08 06:46:11 -0400 [EMAIL PROTECTED] wrote: > Hi, > > I have some questions for experienced jBosS or maybe just ejb experts > here, having implemented systems with lots of asynchronous messagedriven > components. > > The thing I want to design in here is a network of objects communicting > with each other. The concept of message-driven components is just > fantastic. > > I will describe what's going on in my zoo : > > we have lots of objects in there - lets call them beings. These beings > communicate with each other, have different interests, and the whole > system is going to serve people in the physical world with different > intentions. However it is clear that the objects in the server have one > working field - lets say the food industry. > > The objects in there gather data from different datasources : databases, > incoming messages, or even clients connecting to the objects. Paul, a > food deliverer, may have his own EJB in there gathering requests for him > and managing them in a way that is most economic for him when he drives. > His EJB is autonomous, answers requests from other EJBs and just gives > them information, and makes deals for Paul, or even IS Paul, whenever he > is logged in into his EJB. > > Well - I know thats quite a sick vision. > > We have lots of objects in there who wont ever be the representation of a > real-life person. But now come the design issues for this system : > > I decided to design every object in there like "Paul". So everything in > there, or almost everything, will be asynchronous. > And every EJB will be able to communicate with nearly every other, > asynchronously. > > Has anyone in here ever put up something similar ? > > Is there a big trade-off in performance ? > (whenever, in a synchronous design, there are several method calls > waiting on one object, the ejb server is surely handling them in a queue > also - so there are surely queues in synchronous as in asynchronous > design). > > What should I watch out for ? > > My main worry is the performance of a message-driven design. But the > possibilities are just fantastic. > > So my questions are : > - how would you see the performance issue ? > - if performance is acceptable, do you have any design tips for an > asynchronous design ? > - have you ever implemented and been running such a system with jboss ? > - with a large number of messagedriven objects floating around (the > number of objects is larger in the messagedriven design of the system, > than in a synchronous design) > > What would you say ? > > Best regards, Jubin > > > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
