Looking for pros and cons of working with real-time tick data using Druid vs OpenTSDB. Tick data must be ingested in real-time at finest resolution possible and provide an interactive store for analytical queries such as slicing and dicing as well as roll-ups and aggregations.
Hi @dbaev while I won't just say "go for druid" I would suggest that you look at the recent slides and video from the DataWorks summit session on Druid and use it to inform your decision.
Video of presentation: https://www.youtube.com/watch?v=OpuTAOCxq1k
One additional element that may be relevant is that while it's Tech Preview right now in HDP 2.6, it will be supported in the future by Hortonworks, so if having a fully supported solution from a single vendor is also important to you, that might also play a part.
Yes Go for druid ! I want to start with disclaimer i am a druid committer. First i want to point that as an engineer i don't believe that there is a single query engine that can be always be better that all the other solutions, it is all relative to the use case you want to solve. Now let's get to why Druid and not OpenTSDB for real-time stream application ? Therefore the use case keyword here is real time streaming applications.
Well for the simple reasons are:
In my opinion those are the key element to look for when i am building realtime streaming application. To my limited knowledge i am not aware if there is any integration or production use cases with real time streams and OpenTSDB.