How to achieve multi-tenancy in the context of Kafka and storm?

Question

What are the best practices, for building a multi-tenant app in the context of Kafka and storm?

For example: creating topic for each tenant and consume multi-topics spo

Answer 1

Don't consider my answer as the "best practice" because I'm not Kafka expert, but in case it helps: we faced a similar design scenario (one Kafka endpoint available to multiple teams that acts as a central point for event creation and routing). After pondering different alternatives, we decided what you suggest: to have one topic per application (you could say tenant), customizing the topic (partition, limits, etc.) according to the application needs.

Hope this helps.