Uploaded image for project: 'Repose'
  1. REP-5234

SPIKE: Alternate Datastore Implementation

    Details

    • Type: Spike
    • Status: Resolved (View workflow)
    • Priority: Unprioritized
    • Resolution: Done
    • Affects versions: None
    • Fix versions: NORE
    • Components: None
    • Labels:
      None
    • Epic Link:
    • Sprint:
      Sprint 139
    • Capitalizable:
      True

      Description

      NOTE: The PR for REP-5265 Resolved (which is a Minor version update) is associated with this Spike.

      The distributed datastore is fundamentally broken in a highly dynamic environment. One possible solution would be to externalize and centralize the datastore into persistent storage of some sort. Another would be to replicate data across nodes (using something like Hazelcast, perhaps).

      Acceptance Criteria:

      • Determine the level of effort required to update Repose to support the new datastore.
      • Create stories to make the updates.
      • Make sure we refer to it as the "remote datastore" instead of the "distributed datastore".

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                wdschei Bill Scheidegger
                Reporter:
                damien.johnson Damien Johnson
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: