Use Cases

Sub-second queries at high concurrency, on data that changes by the second

Point lookups, complex joins, log search, and vector retrieval run in one engine. Start with the workload you have now and add the next one without adding another database.

What teams build

Four workloads, one engine

Every number below comes from a customer story published on this site. Follow any of them to the full write-up.

Use case 01

Real-Time Analytics

Interactive dashboards and customer-facing data products that answer in milliseconds, on data that is seconds old rather than hours stale. Multi-table joins and high-cardinality filters run without pre-aggregating or denormalizing first.

KwaiJD.comPlanetAve.aiBYDNetEase
Learn more
JD.com

China's largest retailer by revenue runs live A/B testing and conversion-funnel dashboards on Doris, chosen after an evaluation against Druid, Elasticsearch, and ClickHouse. Peak ingestion reaches 600 million records in 10 minutes.

10B+
Rows processed daily
10K
QPS throughput
150ms
Minimum query latency
Read the story
Use case 02

Observability in the AI Era

Logs, metrics, and traces on one copy of the data, with inverted indexes serving keyword search from the same tables the aggregations read. The most cost-effective path off an Elasticsearch or Loki observability stack.

MiniMaxNetEaseTencent MusicAdvance.AI
Learn more
MiniMax

The AI company behind Talkie outgrew a Loki-based stack where regex queries scanned entire datasets and spiked compute. Its Doris-based platform now serves petabyte-scale log search, with 5:1 compression and tiered storage behind it.

Under 2s
Across 1B log records
10 GB/s
Write throughput
70%
Lower storage cost
Read the story
Use case 03

Data Warehousing

Interactive analysis and reporting on open lakehouse formats. Query Iceberg, Hudi, and Paimon tables in place with Doris as the acceleration layer, and offload the batch warehouse without rewriting the data layout.

PlanetXiaomiSF TechnologyTencent MusicHaidilaoMeituan
Learn more
Planet

Global payment infrastructure that moved analytics off Snowflake. Payment data that took 5 to 10 minutes to become queryable now lands in 1 to 2 seconds, and 100 concurrent user dashboards average 1.2 seconds.

80%
TCO reduction vs Snowflake
1.5s
Multi-table JOIN response
3B
Events per day
Read the story
Use case 04

Context Engineering

Vector similarity, BM25 full-text, bitmap labels, and JSON filtering in a single SQL statement, over data that is fresh enough to answer an agent. One retrieval layer for RAG, agent memory, and training-set management.

ByteDanceAISpeechXiaomiBaiduNetEaseTencent
Learn more
ByteDance

Per-segment BM25 caused ranking instability on every segment merge for billion-vector talent matching. Global statistics with progressive filtering fixed it, and storage shrank from 10TB on 20 servers to 500GB on one.

94%
Relevance, from 58%
400ms
Latency at billion scale
384x
Compression with IVPQ
Read the story
Comparisons

Replacing something already in production?

Most teams arrive with an engine they have outgrown. These are the migrations they ran and what changed afterwards.

All comparisons
Alternative to

ClickHouse

Higher concurrency, more efficient joins, easier maintenance, and MySQL-compatible SQL, without the operational overhead.

64–90%
Latency reduction
Under 5%
Slow queries, was 35%
3M/s
Rows ingested per node
We dropped slow query rate from 35% to under 5% and reduced point query latency from 250ms to 12ms. Real-time campaign attribution across 4,000 query templates and 700 fields now runs on one engine instead of three.
Engineering Team, Kwai
Alternative to

Elasticsearch

Cut storage and write costs with high compression, and get full JOIN support with superior analytical query performance.

80%
Lower operating cost
4x
Write performance
72%
Storage reduction
By replacing our Elasticsearch cluster with Doris, we unified content search and analytics into a single platform. Write performance improved 4x, storage dropped 72%, and overall operational costs were cut by up to 80%.
Data Engineering Team, Tencent Music
Alternative to

Trino / Presto

Unify your data warehouse and lakehouse query engine into one, and outperform a query-only engine.

3x
Faster P95 latency
48%
Hardware cost savings
96%
Data cache hit rate
Queries taking longer than 50 seconds dropped from 8% to just 1.5%. We migrated 100% of our ad-hoc and BI platform query workloads off Presto.
Data Platform Team, SF Technology
VeloDB vs.

Snowflake

Real-time analytics with higher concurrency and faster queries, at a fraction of the cost.

80%
TCO reduction
1–2s
Freshness, was 5–10 min
100
Concurrent dashboards
Payment data that took 5 to 10 minutes to become queryable on Snowflake now lands in 1 to 2 seconds. Multi-table JOINs return in 1.5 seconds, against 8 seconds on Snowflake.
Parth Soni, Senior Data Engineer, Planet
VeloDB vs.

Redshift

Higher concurrency, a flexible storage-compute architecture, and seamless, non-disruptive scaling.

  • Multi-compute, shared-data architecture isolates ingestion from serving
  • Deploys on AWS, Azure, and GCP, or in your own VPC
  • Scales without pausing writes or resizing a cluster
See the comparison

Start with one workload

Spin up a cluster in under 60 seconds, or talk to an engineer about the workload you have in mind.

Need help? Contact us!