> I know Coherence is a distributed cache and that you can use it (although not very well explained in your site) to build a data grid.
Any application that uses Coherence can be a part of (or a client of) a scale-out data grid that is provided by Coherence. There is nothing extra to do, you just start more instances of the application and the data grid gets larger (more capacity) and the conceptual interconnects exponentially increase the resiliency of the data fabric.
The "space" (if you will) is managed by the grid, not by some particular server, so the more servers you add to the grid, the larger and faster and more resilient the data grid becomes.
> I looked at Javaspaces because of the tuple-based programming model
The JavaSpace model (tuples, LINDA, etc.) is totally different than the approach that we took in Coherence. Basically, if you want a tuple space approach in Java, then you should use the JavaSpaces APIs. (i.e. The right tool for the right problem approach.)
> Although I never considered Coherence to build our virtual compute server I did consider using JGroup, if it helps to clarify my point.
Again, I think that if you have a tuple model, then JavaSpaces is the best API choice for Java.
Other models become extremely unwieldy to squeeze into a tuple space based implementation.
Peace. |
java.net RSS Feeds
