[UXPROD-342] Message Queue Business Logic to Partition Data by TenantID Created: 05/Mar/18  Updated: 05/Nov/18  Resolved: 05/Nov/18

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2018

Type: Story Priority: P3
Reporter: VBar Assignee: Unassigned
Resolution: Done Votes: 0
Labels: analytics, kafka
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-1287 Advanced Message Queue Business Logic... Open
Relates
relates to UXPROD-332 Message Queue for Data Extraction Closed
relates to UXPROD-343 Partition Transactions into Kafka Topics Closed
Front End Estimator: VBar
Back End Estimate: Medium < 5 days
Back End Estimator: VBar
Development Team: EBSCO - FSE

 Description   

Initial implementation for Kafka.

Tenant message streams are partitioned using Kafka Topics. Each Kafka topic will contain only transactions from a single tenant context. It should still be possible to create multiple Kafka Topics (to support different message streams) for a given tenant context.

Future stories will be used to allows streams (and thus topics) to hold transactions from multiple tenants at once.


Generated at Fri Feb 09 00:07:28 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.