Nader,
> Background: > ----------------------------------------------------- > It is a common practice to scale up by running several instances of a > container system, e.g. Merlin, on multiprocessor machines and on several > computers. This would require communication among container systems > running in different JVMs. There exist many different techniques: simple > Round Robin external routing, shared memory systems like JavaSpaces, > persistant shared memory systems involving RDBM and finally mobile codes > (as in mobile agents). > ---------------------------------------------------- > > Question: > Is there any specification/best practice/mechanism in Merlin? Again to my knowledge nothing exists. Basically we're talking about "clustering" components and/or component failover. Things like the stateful or the stateless nature of components might need to be considered and state propagation must be handled in the stateful case. Component affinity must also be considered. There are several factors I could go on ad infinitum. Some will think it is impossible to achieve component clustering due to the perceived need to consider the nature of each component. I don't think this is the case. If a good clustering framework can be devised then yeah sure I think components can be clustered. Perhaps this can be a facility of the container - just thinking out loud. For the time being I myself am experimenting with things like JGroups for state propagation. This is something I need to do for enabling replication for Eve. However the same technology can be used in a container to replicate things like configuration and component state. Feel free to pick up this torch and run with an attempt to "cluster" components within multiple containers within multiple JVMs. It takes a brave soul but I have a feeling that you may be the right guy for it. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
