Your comment is really confusing.
Which are the Javaspaces tremendous bottlenecks? I am using a Javaspaces implementation exactly for the same purpose explained in this post and works great.
Javaspaces memory limitation? or JVM memory limitation?
If you meant Javaspaces memory limitation let me point you out that your comment is as incoherent as saying "JBDC memory limitations", Javaspaces is a spec (API) not an implementation. Are you referrying to a specific implementation of the spec (Outrigger, Blitz, Gigaspaces, etc.)?
A shared virtual memory is a much better option ?
Javaspaces is not a spec for a distributed database!
In fact it is a spec for a Jini distributed shared memory service.
On your point about maturity...Javaspaces is a Java spec that follows the Tuple-based programming paradigm developed at Yale University and implemented in the Linda Programming Language in the early 80's. Linda is used for parallell programming.
The beauty about Javaspaces is the simplicity and power of the tuple-based programming model and the fact that it is a JINI service. |
java.net RSS Feeds
