These three projects are trying to wrap my head around and they all handle different problems that arise when trying to cluster.
- What are the specific problems, each of them are trying to solve, and how are these problems different from each other?
- How does clustering with each of them differ from the clustering app server (such as built-in clustering capacity of a jabos or glassfish)?
- Do these problems solve different ways in order to warrant their use on a similar project? Or are they competing with each other and there are different solutions to the same / similar problem?
Thank you in advance for any insight into these curious, yet elusive frameworks!
Hajlcast Classing can be used for TCP based address or multicasting Allows Yam. It supports maps, multimaps, lists, queues, themes for disk based backups, you must apply the load / store interface
With eHatch, you can add RMI replication for JCGroup, JMS or Cache. You can use.
In short, if you are looking for a distrubuted data cache / grid, hazelcast or ehacas, then there will be tools to see - if you are looking for work distribution using a library and existing Not to worry about Data Grid Cache, Jaguops will work for you.
Comments
Post a Comment