Support tuneable consistency at the table level
Registered by
Keith Newstadt
A common reservation about moving to a NoSQL solution is the loss of consistency. While often this can and should be addressed with application improvements, there are cases when stronger consistency is important. For example, an application's end user registration often needs to be complete and guaranteed before the end user can start to use the application. Application developers need to be able to specify that some data, such as user profile data, needs to be strongly consistent.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Keith Newstadt
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- Accepted for future
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.