[jira] Created: (RIVER-394) Distributed Transaction Manager

["Tom Hobbs (JIRA)" <ji...@apache.org>]

Distributed Transaction Manager
-------------------------------

                 Key: RIVER-394
                 URL: https://issues.apache.org/jira/browse/RIVER-394
             Project: River
          Issue Type: New Feature
            Reporter: Tom Hobbs


River-393 was created to start recording the details needed to begin designing and building a distributed Java Space.  After discussion of this on dev@ a point of view was raised that a distributed transaction manager would be a more useful component to have before we can realistically think about distributed spaces.  From the list;

"I'm actually inclined to tackle distributed, resilient transaction management first, for two reasons:
1. I'm dubious about whether a distributed JavaSpace would really be useful without it.
2. I think it may be useful in maintaining consistency among duplicated copies of the same entry."

We also have an idea of the kind of SLA a DTM might be expected to fulfill.  Again, from the list;

"The SLA that I, the enterprise developer of resilient HA system,
care about is that once the operation completes (call it transaction
commit), the state transition is preserved even if N arbitrary
failures occur, AND that the system has a computable T time to restore
itself from 'reduced HA' to 'full HA' within which additional failures
beyond N is not guaranteeing preservation of state transition. The
larger the T, the more N I need which increases my cost profile."

This Jira is just another place to start recording thoughts so we can then start thinking about how to build and test such a component.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira