2 ms·
The CTO at my first job out of college was the chief architect for JavaSpaces. I think we'd used it in an early version of the product but had migrated away fr
by nostrademons 8y ago
The CTO at my first job out of college was the chief architect for JavaSpaces. I think we'd used it in an early version of the product but had migrated away from it by the time I joined full-time.
Aside from the fairness issues that other commenters mention, tuple-spaces work at an awkward level of abstraction. You can easily implement many other distributed concurrency models with them - semaphores, message queues, producer/consumer channels, broadcasts, even MVCC and transactions - but oftentimes, in the application it's more natural to just use the more specific abstractions. For example, you could implement a message queue by putting tuples of [type tag, sequence number, ...data] in and taking out the next message of a given type - but usually you'd want guarantees that there are no name collisions among type tags, and that sequence numbers are never skipped, and a mechanism to resend missing messages if for whatever reason they aren't produced correctly. At that point you'd rather just use golang-style channels or a real message queue library rather than roll that on top of the tuple-space.
There are relatively few problem domains I can think of that map directly to a tuple-space, without building some other concurrency abstraction on top of it. Dependency graphs and workflows, perhaps, but there are other libraries to handle that specific problem which also handle things like tracing, debugging, and error correction.
- ralphc 8y agoEarly to mid 2000's a product I worked on had a messaging abstraction that you could use JMS, MQSeries, MSMQ, etc. We tried, really tried, to use JavaSpaces but it had no FIFO guarantee. You could theoretically add and get tuples and one could stay in the space for days. A non-starter for that.