Can Apache Pinot replace your OLTP database?
summary
Compares Apache Pinot to OLTP using a live Docker demo that wires MySQL → Debezium → Kafka → Pinot and shows CDC-driven real‑time upserts and backfill with the Minion bootstrap; demonstrates joins and per‑state aggregations with sub‑second latency. Explains columnar segments, bloom pruning, inverted/range/geospatial indexes, star‑tree index, HLL/Theta sketches and compaction. Claims production scale: LinkedIn clusters at ~200k QPS, billions of keys, petabyte scale; conclusion: Pinot can replace OLTP for hybrid serving and user‑facing analytics but not all transactional workloads.
AI-written summary · about
chapters (12)
- 0:00Introduction and agenda
- 1:06What is OLTP database
- 3:13OLTP use cases and challenges
- 10:46Apache Pinot overview
- 13:14Offloading analytics to Pinot
- 17:43Pinot data bootstrap and backfill
- 19:11Replacing OLTP with Pinot
- 21:00Pinot query optimization techniques
- 27:24Pinot indexes and performance
- 29:07Pinot real-time upserts
- 32:35OLTP vs Pinot comparison
- 35:03Conclusion and Q&A
related talks
54mAn Introduction to Apache Pinot
34mNext generation OLAP stack using Apache Pinot
49mIntroduction to Real-Time Analytics with Apache Pinot
44mUSER-FACING, REALTIME ANALYTICS USING APACHE PINOT
47mReal-time analytics for your users with Apache Pinot
39mFaster Analytics for Fast Data with Apache Pinot and Flink SQL
38mReal-Time Analytics: Going Beyond Stream Processing with Apache Pinot
34mReal-Time Analytics: Going Beyond Stream Processing with Apache Pinot
