kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Avi Flax <avi.f...@parkassist.com>
Subject Re: Architecture recommendations for a tricky use case
Date Wed, 05 Oct 2016 23:32:32 GMT

> On Sep 29, 2016, at 16:39, Ali Akhtar <ali.rac200@gmail.com> wrote:
> 
> Why did you choose Druid over Postgres / Cassandra / Elasticsearch?

Well, to be clear, we haven’t chosen it yet — we’re evaluating it.

That said, it is looking quite promising for our use case.

The Druid docs say it well:

> Druid is an open source data store designed for OLAP queries on event data.

And that’s exactly what we need. The other options you listed are excellent systems, but
they’re more general than Druid. Because Druid is specifically focused on OLAP queries on
event data, it has features and properties that make it very well suited to such use cases.

In addition, Druid has built-in support for ingesting events from Kafka topics and making
those events available for querying with very low latency. This is very attractive for my
use case.

If you’d like to learn more about Druid I recommend this talk from last month at Strange
Loop: https://www.youtube.com/watch?v=vbH8E0nH2Nw

HTH!

Avi

————
Software Architect @ Park Assist
We’re hiring! http://tech.parkassist.com/jobs/

Mime
View raw message