Been there -- a distributed ExecutorService.

Wed, 17 Sep 2008 00:00:00 +0000

I happened to run across a new open-source project today I had not previously heard about: Hazelcast.

What really piqued my interest was the implementation of a distributed ExecutorService as I wrote something of similar functionality to façade Orbitz’s Jini infrastructure. The design and implementation solved a couple primary objectives:

add timeouts to Jini which is unfortunately lacking such a feature
bound the number of concurrent requests being processed
bound the number of threads created for request processing

The design was elegant, imo, because the exact same code worked either client or service-side – it just mattered which way you twisted your head – and masked the complexities of both Jini and the ExecutorService. The timeouts were managed via the Future and the throttling of requests and threads by configuring the backing Queue and pool size. Spring wiring entirely hid the remote invocation machinery from the caller. In almost every case there were no code changes and the timeout and throttling features could be turned on and tuned entirely through a configuration change.

Distributed-System on

Been there -- a distributed ExecutorService.