Let me give some simple explanations as below. Since I am more familiar with Kylin, these explanations may not be 100% accurate. :-)
1. Druid is more suitable for realtime analysis. Kylin is more focus on OLAP case. 2. Druid has good integration with Kafka as realtime streaming. The realtime capability of Kylin is still under development. 3. Druid use bitmap index as internal data structure. Kylin use bitmap index for realtime data and molap cube for historical data. 4. Kylin provide ANSI SQL. Druid provide specific query language. 5. Druid has limitation on table join. Kylin support star schema. 6. Kylin has good intergration with BI tools, such as Tableau or Excel. Druid can't integrate with existed BI tools. 7. Since Kylin support molap cube, it has very good performance for complex query on billion level data set. Since Druid need to scan the full index, the performance may be hurt if the data set and query range is too big. Thanks Jiang Xu ------------------ ???????? ------------------ ??????: ????????(??????Kevin) <[email protected]> ????????: 2015??03??20?? 14:44 ??????: dev <[email protected]> ????: shigira <[email protected]> ????: Kylin vs Druid Hi, A quick question, how do you look at Kylin differently from Druid, another tool that is built for providing large quantity of analytic data with low latency? Are two tools to solve the similar problem with different approaches? Thanks! Kevin
