[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: |
|
||||||||||||||||||||
| 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. |