# Which columnar database solution works best for log analytics and time-series style data where query patterns are append-heavy and dashboards need to refresh in near-real-time?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">I'm compiling a piece on real-time analytics infrastructure, and which<a class="a a--md" elv="true" href="https://www.g2.com/categories/columnar-databases"> </a><a class="a a--md" elv="true" href="https://www.g2.com/categories/columnar-databases">columnar databases</a> work best for log analytics and time-series data, where query patterns are append-heavy and dashboards need to refresh in near-real-time, is the question where general-purpose options tend to fall short. Three stand out specifically for this pattern:</p><ol>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/druid/reviews"><strong>Apache Druid</strong></a><strong>:</strong> Data partitioned by time out of the box means time-based queries perform exceedingly well, with real-time ingestion from Kafka and aggregations completing fast enough to power live customer dashboards. The architecture spans 6 core services though, which makes deployment and management complex. Have you run into the multi-tenancy gaps or join limitations in a production append-heavy environment?</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/startree/reviews"><strong>StarTree</strong></a><strong>:</strong> Sub-second queries stay consistent even during high-traffic workloads, with streaming ingestion that handles high-volume event data and pre-aggregations that keep dashboard queries fast at scale. Indexing and tuning takes real expertise to get right upfront. Does the onboarding complexity change materially for teams coming from a traditional SQL warehouse?</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/clickhouse/reviews"><strong>ClickHouse</strong></a><strong>:</strong> Real-time aggregation on large event volumes with a compression algorithm that makes both ingestion and retrieval fast, and strong Grafana integration for dashboard use cases. Materialised views are limited to a single join currently, which requires upfront planning on how data is structured.</li>
</ol><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">For teams running append-heavy pipelines with near-real-time dashboard requirements, which held up as ingest rate scaled and concurrent dashboard users increased?</p>

##### Post Metadata
- Posted at: 20 days ago
- Author title: Marketing Executive
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;ClickHouse makes a lot of sense here, especially with append-heavy patterns. Druid and StarTree feel more purpose-built, but they come with their own setup tradeoffs. Curious, did anything actually hold up once the ingest rate and dashboard concurrency both ramped up?&lt;/p&gt;

##### Comment Metadata
- Posted at: 20 days ago
- Author title: Writer





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: about 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: about 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: about 13 years ago
  - Comments: 4