Build a compute server with JavaSpaces Part 3. Coordinate your Jini apps with JavaSpaces Part 4. Explore Jini transactions with JavaSpaces Part 5. Make your compute server robust and scalable Simple as it is, the compute server has some impressive qualities. There's no need to bring the compute server down or install new task code on various machines, since executable content is built into the task entries themselves.
Workers can come and go from the compute server, without requiring code changes or reconfiguration.
Despite its admirable properties, the compute server still isn't quite ready for the real world yet. In this article, I'll show you how to make two big improvements to gear the system up for real-world use. If you read Part 4 of this series, you've probably guessed that one of the compute server's weaknesses is that it neglects to account for the presence of partial failure. Armed with what you know about Jini transactions from that article, I'll now have you revisit the compute server code and show you how to make it more fault tolerant. Under some circumstances, reliance on one space may introduce a bottleneck, so I'll revisit the compute server code to show how you can make use of multiple spaces to allow for greater scalability.