If you have something like Kafka before you insert your events into CH, you could consider enriching the event data by connecting with your Postgres data. That way, you still retain a flat CH table which should work just fine.
Wonderful effort folks. You are definitely creating something that's going to last a long time and help a lot of people. Zerodha is a company I will adore from now on.
Would this be a replacement for something like Divolte? If yes, any specific reason why one should choose EventNative over Divolte, except for the "made in go" argument?
Took a look at their github. Great product! However, it requires Hadoop or Kafka cluster setup (=devops resourced). We designed kSense to be a simple as possible and have as few dependencies as possible.
Besides, if you want to data to land at BQ/CH or RedShift with Devlot, you'll need add a 3rd-party Kafka->DWH layer. I'm pretty sure there'are many oss options. Not sure if they can automatically generare SQL schema from JSON object like EventNative
We haven't used Druid yet. We did a high level comparison among Druid, Clickhouse & Pinot from material available on the internet. Apparently, all 3 have similar mechanisms. But druid is a little expensive to deploy when at a smaller scale. Clickhouse seems to be performant too. We seem to be inclining towards Clickhouse.
I appreciate it! Druid has been in our priority as we need to process data on a very large scale. I see your point that Druid might be a little expensive when deploying at a small scale! Thanks!
