Druid, Kafka and your favourite Dashboard
What do you like best?
Druid is amazingly fast and has built-in connectors for most of the popular datasources .
It supports variety of dashboards which makes druid a perfect choice for any Real Time Streaming Application .
What do you dislike?
Druid natively queries in Json format which is hard to pick up for a SQL user.
Rollover queries are not dynamic . Example - If you want to roll up for a specific time of one day to a specific time of another day , that might not be possible .
Web GUI is also not so user friendly for a business user .
Missing operations friendly cluster manager console.
Druid needs a dedicated server and cannot utilise existing Hadoop resources.
Recommendations to others considering the product:
Druid is a perfect database to power real-time analytic workloads for event-driven data.It is fast, has column-oriented storage and is a time series database . It is just fits fine in any big data stack .
Note - Druid might not be a good choice if you are a heavy dependent on joins .It might slow down the performance
What problems are you solving with the product? What benefits have you realized?
We needed a database where we could persist our data from Kafka and could also do some rollup .
It was also required that the database should be fast enough to do aggregations when displaying on the dashboard . Everything had to be in realtime .
Druid was fast and capable enough to acknowledge all the requirements.
Built in connectors save much of the time and effort while integrating with other applications.
