Re: multi-tenancy without a kafka partition per tenant

2019-10-23 Thread vino yang
Hi Constantinos, I think your analysis is correct, if you have a multi-tenant scenario, but there is no distinction in Kafka. Then Flink can't treat different tenants differently. It is easy to form a data hotspot problem for the difference in the data volume of different tenants. A compromise is

multi-tenancy without a kafka partition per tenant

2019-10-21 Thread Constantinos Papadopoulos
We have a multi-tenancy scenario where: - the source will be Kafka, and a Kafka partition could contain data from multiple tenants - our sink will send data to a different DB instance, depending on the tenant Is there a way to prevent slowness in one tenant from slowing other tenants