Page Comparison

...

Overrides/Supersedes 

When applicable, provide links to all DRs that this DR overrides or supersedes 

RFC 

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 decisionNot Applicable

RFC 

https://github.com/folio-org/rfcs/blob/master/text/0002-kafka-tenant-collection-topics.md

Stakeholders

Olamide Kolawole 

Contributors

Olamide Kolawole 

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 here

Implications

• Pros
  • Provide a link to RFC when applicable
• Cons
  • Provide a link to RFC when applicable

Other Related ResourcesThis will allow FOLIO's maximum number of tenants in a cluster to not be bound too early by Kafka resources and consequently reduce costs to host a suitable Kafka cluster for a corresponding multi-tenant FOLIO installation.

Assumptions

• Development will need to occur on module touch points with Kafka to express the enhancements described in the RFC

Constraints

• Kafka topic topology where multiple tenants have their dedicated topics will still be available.

Rationale

Detailed in the RFC

Decision

Provide a configuration option for FOLIO modules to produce messages to a tenant collection topic or a single tenant topic in Kafka.

Implications

• Pros & Cons are detailed in the RFC.

Other Related Resources

Not Applicable