RPC API Versioning
Registered by
Victoria Martinez de la Cruz
At the time of writing, Trove's internal RPC API uses a unified versioned model
for every internal component. If we consider a distributed deployment in which
you normally have several instances for each of the Trove components running
in different nodes, an operator should be able to gradually upgrade those
instances without requiring to stop all services and while having the guarantee
that the communication between components will continue.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Victoria Martinez de la Cruz
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)