Page Properties | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
Provide links to all relevant RFC's
Stakeholders
@mention individual(s) who has vested interest in the DR. This helps us to identify who needs to be aware of the decision
Contributors
List individual(s) sposnoring/advocating for the decisionMikhail Fokanov VBar Marc Johnson
Contributors
Approvers
List TC members voted to approve the change
Background/Context
Explain the need that triggered the need for making a decision
Assumptions
List all assumptions that were made when making the decision
Constraints
List any constraints that lead us to make a certain decision
Rationale
Document the thought process, list reasons that lead to the final decision
Decision
Short summary of the decision goes hereApache Kafka should be used directly in inventory-storage for implementation of domain event pattern, which is needed for both remote-storage integration and the new search module. This direct usage of Apache Kafka should be considered as a special case, as it was for data-import. Also, it is a special case, that storage modules use more than one data storage. For the search module, the performance is significant. Kafka partitioning provides the system with an out-of-the-box mechanism for scaling out modules.
Action items
Assumptions
N/A
Constraints
N/A
Rationale
N/A
Decision
Instance_id should be added to inventory-storage update notifications for items
Implications
- Pros
- Provide a link to RFC when applicable
- Cons
- Provide a link to RFC when applicable
...