This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
The application we intend to build has been divided into seven modules.Earlier we had decided to start the development simultaneously(.. we have ample resources!!) and eventually deploy it in Jboss as one EAR file with different WARs. Now due to deployment concerns we have decided to drop this approach.
We are contemplating on having more than one JVMs each being utilised by say 2/3 modules.Interaction between them would be implemented by Java RMI.To be precise we would have to make sure the modules 1 , 2 and 3 are running in JVM 'A' while modules 4 , 5 and 6 are running on JVM 'B'.And use RMI for any inter module interactions.So what it would imply is that each box would have more than one JVM.Would be going for horizontal clustering for scalability, although thats a different issue anyway.
Please suggest what could be the loopholes.
To repeat what others have said, requires education, to challenge it , requires brains.
Pat Farrell wrote:My suggestion is: Do not use RMI
Pass messages, using REST
IMHO, YMMV, etc
Can you explain what makes you conclude this.To me this seems an exaggeration...i mean firstly i don't have to worry if the platform is non-java coz it is not, secondly the whole process of marshaling from java objects to xml is an issue..i think we should prefer communicating using RMI at least in this scenario.Please pitch in your suggestions.