Xiaohongshu optimized StarRocks querying of Lance-format training datasets, implementing TopN delayed materialization, scan range splitting, metadata caching, and balanced index scheduling, reducing cold vector search from 15s to 5.9s and hot from 4.5s to 1.5s on 7B rows.
Alibaba Cloud's EMR Serverless StarRocks integrates Lance's vector search into its distributed SQL engine, enabling single-query hybrid retrieval and relational analytics on multimodal data, demonstrated by a 2-billion-vector e-commerce case achieving 16x faster hybrid search and 40x lower latency.
This article details integrating DuckDB into Spring Boot for embedded OLAP analytics, covering tenant-isolated connection pools, secure view-based file access, streaming exports via COPY and cursors, SQL injection guards, and performance tuning for ad-hoc Parquet/CSV queries without a separate cluster.
The article details StarRocks' integration with the Lance columnar format for multimodal lakehouse workloads, covering distributed index search, two materialization strategies (non-GLM and Global Late Materialization), and a 2-billion-vector case study achieving 40x latency reduction and 16x throughput over Ray+Lance.
The article provides a decision framework for enterprises evaluating Lakehouse adoption, arguing architecture should evolve with business complexity rather than follow trends. It defines six evaluation dimensions, contrasts Lakehouse with traditional OLAP, outlines phased evolution from basic analytics to streaming Lakehouse and AI data infrastructure, and warns against five common over-engineering pitfalls.
Helix Foundry open-sources a local-first workflow combining HelixDB graph database and DuckDB OLAP to automatically construct enterprise ontologies from disparate SaaS sources, using deterministic entity resolution with AI-assisted descriptions, validated via snapshot-versioned SQL pipelines and human review.
This article provides a practical decision framework for choosing between Apache Doris and StarRocks for real-time OLAP workloads, comparing their architectural origins, licensing, optimal use cases, and guiding teams through self-hosted versus managed deployment decisions based on organizational capacity and query profiles.
This article analyzes two financial risk control lakehouse architectures: DiDi uses StarRocks to unify real-time and batch feature serving with primary-key tables and bucket pruning, while Ant Group replaces HBase and Elasticsearch with Apache Paimon's first-row, partial-update, and sort-compaction mechanisms for long-window deduplication, fast reconciliation, and historical lookback.
WeChat's technical architecture team shares their exploration of adapting OLAP infrastructure for Agentic AI, covering distributed observability with Langfuse and ClickHouse, remote memory services using vector search and FUSE, and access protection mechanisms treating agents as authenticated identities.
StarRocks now fully supports Paimon 2.0, integrating columnar analytics with vector, full-text, and scalar indexes into a single SQL execution framework for multimodal lakehouse workloads, enabling unified data management, retrieval, and relational analysis on object storage without data movement.
StarRocks introduces multimodal capabilities to handle structured, semi-structured, and unstructured data in a single SQL pipeline, combining object processing, full-text and vector search, and lakehouse integration with Paimon and Lance for unified retrieval and analysis.
This article details how to build a production-ready real-time data warehouse using Flink, covering CDC ingestion, event-time processing, dimension joins, upsert aggregation, state TTL, checkpoint tuning, exactly-once verification, and a pre-launch checklist for reliability.
Enterprise data platforms face common questions—why add a data warehouse when MySQL or Oracle exist, why introduce a data lake after a warehouse, and what problems NoSQL, ClickHouse, or Doris solve—this article breaks down six storage technologies, their core use‑cases, and how to choose among them.
This article provides a comprehensive overview of data warehouse implementation, covering DDL‑based creation, the role of ETL processes, the functions of OLAP/BI tools, data cube operations, and the trade‑offs among MOLAP, ROLAP, and HOLAP architectures.
The article walks through a systematic method for selecting the right storage technology—relational OLTP, search engine, OLAP, or time‑series—based on query intent, data volume, latency tolerance, and consistency needs, using an e‑commerce “optimal store” scenario to illustrate the decision process and practical trade‑offs.
This article shares production lessons from integrating Spring Boot with Apache Doris for real-time data warehousing, covering connection pool tuning, data model selection, ingestion methods, materialized views, Colocate Join optimization, resource isolation, compaction tuning, BI tool integration, and cluster operations.
This guide compares Doris, ClickHouse, and StarRocks for billion‑row real‑time analytics, outlining their strengths and weaknesses across write throughput, update handling, join performance, concurrency, cost, and operational complexity, and provides concrete modeling, ingestion, query governance, and fault‑tolerance recommendations to help teams choose the most suitable OLAP platform.
This article explains why online transaction databases (OLTP) should not be used for multi‑year analytics, outlines the four core characteristics of a data warehouse, details the ETL process, compares star and snowflake schemas, contrasts data warehouses with data lakes, and guides you through selecting Lambda or Kappa architectures using a concrete retail‑store scenario.
The article details how Taotian Group’s senior data engineer Zhu Ao designed a lake‑stream integrated architecture using Fluss for second‑level real‑time storage, Paimon for minute‑level lakehouse persistence, and StarRocks as a unified OLAP query layer, achieving over 50% faster development and more than 80% cost reduction.
The article compares four emerging data‑lake‑for‑PostgreSQL solutions—Databricks LTAP, EDB Fusion Analytics, Snowflake pg_lake, and pgEdge's ColdFront—highlighting ColdFront's unique transparent Iceberg layer, writable cold data, DuckDB integration, and the strategic trade‑offs developers must weigh when choosing a modern OLTP/OLAP/AI architecture.
When a production MySQL query joins ten tables and exceeds 30 seconds, a systematic approach—starting with EXPLAIN analysis, profiling, and configuration checks—combined with layered optimizations such as indexing, join order adjustment, query splitting, temporary tables, materialized views, OLAP engines, and vertical partitioning—can dramatically improve performance.
This case study details how Vivo’s marketing automation platform evolved its data‑driven architecture—from a Presto‑based wide‑table design, through a Bitmap optimization, to a StarRocks migration—addressing performance bottlenecks, reducing resource costs, and enhancing data security.
The article analyzes why traditional row‑oriented databases struggle with high‑volume analytics, introduces DuckDB as an embedded columnar engine for Go, presents benchmark results of up to 18.6 M rows per second writes and 6 M rows per second scans, walks through the Appender API code, and outlines the trade‑offs and ideal hybrid architecture.
This article explains how backend engineers should rethink table design, indexing, partitioning, and key strategies when migrating attendance data from MySQL's OLTP model to Apache Doris 2.1.7's OLAP architecture, providing concrete DDL examples and practical tips.
The article examines why MySQL’s transaction layer remains robust while its analytical capabilities lag, outlines enterprise demands for simultaneous OLTP and OLAP workloads, introduces DuckDB’s lightweight yet powerful engine, describes AliSQL’s integration of DuckDB for full MySQL compatibility, and presents TPCH benchmark results showing a dramatic performance boost for analytical queries.
During Double‑11 mega‑sales, Taobao Group faced exploding OLAP query traffic, costly data sync pipelines, and slow near‑real‑time analytics, so they unified real‑time and batch data in Paimon, leveraged StarRocks for high‑performance lake queries, tuned cluster settings, and saved nearly ten‑million yuan annually while cutting refresh latency by 80%.
OLTP handles real‑time transactional workloads with low latency and high concurrency, OLAP is optimized for large‑scale analytical queries on historical data, and HTAP combines both to support simultaneous transaction processing and analytics; the article compares their characteristics, typical use cases, and popular implementations to guide database selection.
This guide explains the core data‑warehouse terminology—from ODS, DWD, DWS, and ADS layers, through fact and dimension tables, SCD handling, partitioning and bucketing, to data quality dimensions, common data issues, ETL vs. ELT, data lake vs. warehouse, and OLTP/OLAP concepts—providing a complete reference for new data engineers.
This article explains how Taotian Group unified real‑time and offline data using Paimon as lake storage and StarRocks for high‑performance OLAP, eliminating costly sync pipelines, cutting refresh time by about 80%, saving nearly ten million yuan annually, and detailing the architecture, cluster safeguards, configuration tweaks, monitoring, and future roadmap for large‑scale promotional events.
The article explains why scattered, unprepared data hampers analysis, defines data warehouses versus traditional databases, outlines the three‑layer architecture (ODS/Staging, DWD, DWS/ADS), details the ETL process, introduces dimensional modeling, and discusses metadata, data‑quality management, and emerging cloud‑native and real‑time trends.
This article outlines a comprehensive roadmap for data warehousing, covering fundamental concepts, essential big‑data tools, practical implementation steps, advanced architectural topics, and emerging trends such as cloud‑native warehouses and machine‑learning integration, helping readers build a solid knowledge base.
This article analyzes why StarRocks multi-table joins on Paimon/Iceberg tables remain significantly slower than internal tables even after cache warming, detailing six root causes across storage format, data layout, caching, execution engine, metadata, and version management, plus four optimization strategies to narrow the gap.
Despite five years of hype around HTAP databases, most enterprises continue to run OLTP and OLAP on separate systems because of performance trade‑offs, data consistency challenges, higher operational complexity, migration costs, and the fact that real‑time analytics is needed only in a small fraction of use cases.
This article details Cisco Webex's migration from a complex Pinot‑Trino OLAP stack to StarRocks, covering the challenges of the legacy system, the step‑by‑step migration process—including storage, compute, and SQL dialect transformation—and the resulting performance gains, cost reductions, and operational improvements.
This article provides an in‑depth technical overview of ClickHouse, covering its OLAP‑focused architecture, key performance features, detailed configuration files, a comprehensive comparison of its many table engines, common troubleshooting tips, and real‑world deployment patterns for recommendation and advertising systems.
As data volumes explode, enterprises struggle with the high hardware, performance, operational, and migration costs of traditional OLAP warehouses, but ByteHouse’s cloud‑native architecture offers a cost‑effective, high‑performance solution that dramatically reduces both explicit and hidden expenses.
This article examines the exploding data volumes that pressure modern enterprises, outlines the explicit and hidden cost challenges of data warehouses, and presents ByteHouse’s cloud‑native architecture and features as a solution for reducing expenses while boosting analytical performance.
This article examines the exploding data volumes that pressure modern enterprises, outlines the explicit (hardware, performance) and implicit (operations, migration) cost challenges of OLAP data warehouses, and presents ByteHouse’s cloud‑native architecture and features as a solution for cost reduction and efficiency gains.
This article examines the exploding data volumes that pressure modern enterprises, outlines the explicit (hardware, performance) and implicit (operations, migration) costs of operating an OLAP‑based data warehouse, and explains how ByteHouse’s cloud‑native architecture reduces both cost categories while delivering real‑time analytics.
Zepto transformed its brand‑analytics platform from a Postgres MVP into a production‑grade, sub‑second real‑time analytics solution by adopting StarRocks, redesigning its data pipeline with Databricks, Kafka, and Flink, and choosing a storage‑compute architecture that supports massive joins and rapid insights.
This article explains how the Tianji advertising platform consolidated heterogeneous MySQL, ClickHouse, and TiDB data sources into a single StarRocks data warehouse, addressing data silos, real‑time performance, and query complexity while improving accuracy, latency, and development efficiency.
This article explores ClickHouse’s high‑performance OLAP design—including its MPP architecture, columnar storage, vectorized execution, pre‑sorting, sharding, replication, index strategies, and compute engine—showing how each innovation contributes to ultra‑fast, scalable data analysis in the big‑data era.
This article details Qunar's transition to StarRocks as a unified OLAP engine, covering the business background, engine evaluation, architecture redesign, observability, high‑availability strategies, query‑performance optimizations, real‑world application cases, community contributions, and future plans.
This article details how Quark’s data platform consolidated multiple analytics engines into a unified StarRocks‑based OLAP solution, covering business background, engine selection, architecture redesign, performance tuning, operational practices, and future plans for scalability and reliability.
This article walks through using MySQL to pivot rows into columns, covering storage concepts, practical CASE‑WHEN aggregation techniques, and detailed SQL examples for sum, count, average and max calculations, while also discussing performance considerations for medium‑scale and large‑scale data workloads.
This article examines ClickHouse’s high‑performance OLAP design, covering its MPP architecture, columnar storage, vectorized execution, pre‑sorting, table engines, extensive data‑type system, sharding and replication strategies, as well as its sparse and skip‑index mechanisms that together enable ultra‑fast analytics on massive datasets.
Facing a flood of data from over 8,000 communities, the Bifeng service team migrated from a monolithic storage‑compute architecture to a StarRocks‑based storage‑compute separation solution, achieving lower costs, higher resource utilization, faster queries, and improved SLA across their property management platform.
This article provides a comprehensive technical overview of StarRocks' query optimizer, covering its evolution, core architecture, multi‑stage optimization pipeline, key optimizations such as multi‑join colocate, low‑cardinality global dictionary, MV union rewrite, and advanced mechanisms like cost‑estimation fixes, query feedback, adaptive execution, runtime filters, join‑reorder strategies, and SQL plan management.
The article details how Apache Paimon, integrated as an external table format in Alibaba’s Dolphin OLAP engine, achieves millisecond‑level query latency and up to 10k QPS through ORC push‑down, manifest conversion, caching, concurrency, and encoding optimizations, outperforming StarRocks and Hologres.
ClickHouse is an open‑source, massively parallel, column‑oriented OLAP database that integrates its own columnar storage, vectorized batch processing, pre‑sorted data, diverse table engines, extensive data types, sharding with replication, sparse primary‑key and skip indexes, and a multithreaded query engine, delivering high‑throughput real‑time analytics on massive datasets.
This article details iQIYI's transition from Impala+Kudu and ClickHouse to StarRocks, describing the OLAP architecture, performance gains of up to 400% in advertising workloads, the technical challenges of data consistency, lake‑warehouse fusion, operational scaling, and the step‑by‑step migration process using a dual‑run platform.
This article analyzes the challenges of Alibaba Mama's brand advertising data warehouse built on a Lambda architecture, introduces Apache Paimon lake storage and Dolphin OLAP engine as a unified lakehouse solution, details implementation steps, performance gains, and business benefits across multiple advertising scenarios.
This article explains how ByteHouse integrates high‑performance GIS capabilities into its OLAP engine, describes its spatial indexing architecture, showcases benchmark results against ClickHouse, StarRocks, PostGIS and DuckDB using the NYC Taxi dataset, and outlines when to choose ByteHouse versus other spatial database solutions.
The article explains ByteHouse's GIS capabilities, describing its R‑Tree and Google S2 spatial index implementation, OGC‑compatible data types and functions, and presents benchmark results that show ByteHouse outperforming ClickHouse, StarRocks, PostGIS, and DuckDB on key geospatial queries.
This article explains how ClickHouse’s columnar storage, bitmap functions, and distributed architecture can be leveraged to store billions of tag bitmaps, combine them efficiently, and support fast group calculations for customer data platforms, while addressing data‑warehouse integration, storage format, and performance challenges.
Facing high costs and scaling limits with ClickHouse, we migrated a 4000‑core, 500TB OLAP workload to StarRocks, achieving 40% cost reduction, 50% storage savings, and up to 30× query speedups through storage‑compute separation, materialized‑view rewrites, and extensive performance tuning.
This article introduces Easy-Query, a Java ORM that offers strong‑typed OLTP and OLAP query capabilities, demonstrates how to define entity classes with many‑to‑many and one‑to‑one relationships, and provides multiple code examples for complex queries, DTO generation, and automatic inclusion of related data.
Tencent Cloud's TDSQL shattered world records in both TPC‑DS (OLAP) and TPC‑C (OLTP) benchmarks, achieving a 7260 M QphDS score at a cost of 37.52 CNY/kQphDS, and the article explains the three self‑developed technologies—MPP execution, parallel execution framework, and columnar‑vectorized engine—that made this performance possible.
This article reviews the emerging lakehouse architecture, outlines its core frameworks such as Hudi, Iceberg, Paimon, Flink, and Doris, discusses their storage‑compute separation, read‑write optimizations, and highlights how companies of different sizes adopt these technologies based on cost, efficiency, and specific business scenarios.
This article examines a fast‑growing company's sales data platform, outlines the data‑access pain points caused by ACL permissions, describes the migration from ClickHouse to ByteHouse, details the optimizer’s rule‑based, cost‑based, and distributed‑plan enhancements, and presents benchmark results showing query speedups of up to sixteen times.
The article describes how Kuaishou transformed its high‑traffic OLAP system from a separated lake‑and‑warehouse architecture using Hive/Hudi and ClickHouse into a unified lakehouse solution powered by Apache Doris, detailing the challenges, design choices, caching and automatic materialization mechanisms, and the resulting performance and governance improvements.
This article introduces Apache Paimon, an open‑source table format that supports batch and streaming reads and writes, explains its architecture, unified storage model, and core concepts such as file layout, snapshots, manifests, data files, partitions, and consistency guarantees.
This article explains the challenges of fragmented metric definitions, the benefits of a centralized indicator platform for unified management, agile development, high‑performance querying, and outlines the architecture, capabilities, construction process, and operational best practices to maximize data value.
This article presents Kuaishou's experience of designing and implementing a Doris‑driven lakehouse integrated analytics system, covering the current OLAP landscape, challenges of data duplication and governance, the new architecture with caching and auto‑materialization, implementation details, performance impact, and future work.
To achieve sub‑second, multi‑dimensional analytics on Bilibili’s hundred‑million‑row datasets, the team built a ClickHouse‑based acceleration layer that combines grouping‑set pre‑aggregation, bitmap (RBM) distinct handling, and a dense dictionary encoding service, dramatically cutting CPU, memory and query latency versus traditional OLAP pipelines.
This article outlines practical production‑level optimizations for Apache Doris compaction, covering vertical, segment, and single‑replica compaction methods, compaction policies, concurrency controls, and data‑ingestion tuning to improve import speed and query performance in OLAP workloads.
This article analyzes why data engineers face endless data‑extraction requests, identifies common missteps in data‑construction practices, and proposes a comprehensive solution based on dimensional modeling, OLAP multidimensional reporting, self‑service tools, and knowledge empowerment to dramatically improve efficiency and scalability.
This article introduces Alibaba Cloud's Hologres real‑time data warehouse, explains its architecture, table and index types, and provides a step‑by‑step guide for setting up instances, importing data, and running OLAP and KV performance tests using TPC‑H benchmarks.
StarRocks combines vectorized execution, a new cost‑based optimizer, materialized views, a real‑time storage engine, pipeline execution, and distributed joins to deliver a unified, high‑performance OLAP solution that supports both traditional and lakehouse analytics while reducing operational complexity.
This article explains ClickHouse’s columnar, MPP‑based design, block compression, LSM pre‑sorting, sparse and skip‑list indexing, and vectorized execution, while also discussing its high‑frequency write challenges, concurrency limits, and production‑grade issues such as Zookeeper load and resource management.
This article introduces Apache SeaTunnel, a modern data integration platform designed for the EtLT era, detailing its architecture, core connector APIs, checkpoint mechanism, model inference, multi‑table synchronization, the high‑performance SeaTunnel Zeta engine, OLAP use cases, community roadmap, and the commercial WhaleTunnel product.
This article discusses the implementation of Apache Kylin as an OLAP engine for logistics data, focusing on optimizing cube building and query performance to handle large-scale, high-dimensional data analytics.
This article presents a configurable OLAP framework that streamlines multi‑dimensional, multi‑metric analysis by separating core and interaction domains, using metadata‑driven modeling, runtime request handling, and Maven‑based integration to accelerate development and improve query performance.
This article examines why data departments get overwhelmed by massive data‑retrieval requests, identifies root causes such as mindset, requirement handling, and lack of tools, and presents a technical solution centered on dimensional modeling and OLAP multi‑dimensional reporting to streamline data access and empower teams.
MetaApp replaced ClickHouse with the open‑source cloud‑native warehouse ByConity, achieving more than 50% reduction in resource costs while delivering comparable or faster OLAP query performance across distinct, retention, conversion, and point‑lookup workloads, thanks to compute‑storage separation, read/write isolation, and minute‑level elastic scaling.
ByteHouse, a cloud‑native data warehouse built on ClickHouse, redesigns storage‑compute separation, introduces a new MPP architecture, rule‑based and cost‑based optimizers, exchange runtime filters, and parallelism techniques, delivering 10‑200× faster query performance on TPC‑DS, TPC‑H and SSB benchmarks and boosting point‑lookup QPS to 32,000.
The ByteHouse performance whitepaper details the cloud‑native data warehouse’s architecture, rule‑based and cost‑based optimizer enhancements, exchange runtime, runtime filters, parallelism and wide‑table optimizations, and presents benchmark comparisons on TPC‑DS, TPC‑H and SSB datasets demonstrating orders‑of‑magnitude query speed improvements.
This article traces PostgreSQL’s evolution from an academic project to a versatile data‑management framework, highlights its extensive extensions, performance benchmarks, and the shifting landscape of OLTP/OLAP, showing how its open‑source extensibility is reshaping the entire database world.
The article details how the Xiaohongshu data warehouse team integrated StarRocks into their offline processing pipeline, replacing Spark for heavy Cube calculations, which reduced job execution from hours to minutes, cut resource consumption by over 90%, advanced daily data output by 1.5 hours, and lowered refresh cost by more than 99%.
By replacing part of its Spark‑based offline pipeline with StarRocks, Xiaohongshu’s data‑warehouse team cut job execution from hours to minutes, reduced resource usage over 90 %, lowered back‑fill cost by 99 %, and accelerated daily data production by 1.5 hours.
This article analyzes why data engineers face endless data‑retrieval requests, identifies common missteps in data‑construction such as demand‑driven development, lack of modeling and OLAP concepts, and proposes a dimension‑model‑based data warehouse with OLAP reporting, tooling, and knowledge‑empowerment to break the cycle.
This article explains how Douyin rebuilt its interest‑circle platform by replacing MySQL with the columnar OLAP engine ByteHouse, achieving roughly a hundred‑fold improvement in query speed, lower hardware costs, and seamless horizontal scalability for massive daily data volumes.
This article details Xiaomi’s practical deployment of Trino, covering its architectural role, core and extended capabilities, performance comparisons, integration with Iceberg and Spark, operational enhancements, multi‑cluster and ad‑hoc query scenarios, future cloud‑storage plans, and a Q&A session.
MetaApp replaced ClickHouse with the open‑source cloud‑native data warehouse ByConity, achieving over 50% cost reduction and faster, more stable OLAP queries by separating storage and compute, simplifying scaling, and improving resource utilization across a range of analytics workloads such as deduplication, retention, conversion and point‑lookup.
This article details Bilibili's transition from MySQL to ClickHouse for live guild analytics, describing data volume challenges, the design of a Unique Engine to overcome ReplacingMergeTree limitations, and performance results for query and write workloads.
Didi leverages StarRocks materialized views with a global dictionary and bitmap aggregation to perform real‑time, high‑cardinality precise deduplication, automatically rewriting queries and refreshing views, cutting query latency by ~80%, reducing resource use ~95%, and boosting concurrent QPS up to 100‑fold, while planning further automation and bitmap optimizations.
StarRocks’ materialized view feature lets Didi replace costly fuzzy deduplication with precise, high‑concurrency deduplication for real‑time dashboards, using global dictionary mapping, layered ODS/DWD/ADS views, synchronous and asynchronous refreshes, and transparent query rewrite to cut query latency by 80% and boost QPS dramatically.
This article provides a comprehensive overview of open‑source OLAP technologies, examines various business scenarios and data‑lake architectures, and details StarRocks' core features, performance optimizations, and future development plans within the EMR ecosystem.
Facing rapid data growth, Xingyun Retail Credit transitioned from traditional OLTP systems to an Apache Doris‑based OLAP solution, detailing the data demand generation, OLAP engine selection challenges, multi‑stage implementation, performance gains, data‑warehouse construction, and future roadmap for scalable analytics.
This article details Didi's evolution from a multi‑engine OLAP stack to a unified StarRocks solution, explains the design of global dictionaries and materialized views for real‑time dashboard acceleration, and shares performance results, challenges, and future optimization directions.
This article details Didi's evolution of OLAP systems, the adoption of StarRocks for high‑performance MPP analytics, and how materialized views, global dictionary mapping, and transparent acceleration were engineered to boost real‑time dashboard queries while outlining performance gains, challenges, and future optimization plans.
This article presents Didi's practical experience with StarRocks materialized views, covering the evolution of its OLAP architecture, the challenges of previous engines, the adoption of StarRocks, the design of materialized view acceleration for real‑time dashboards, and future optimization directions.
This article presents Jushuitan's cloud‑native OLAP architecture, covering business background, data‑warehouse evolution, real‑time processing with Flink, Hologres, and Aerospike, and detailed logistics‑warning use cases, followed by technical challenges, future outlook, and a Q&A on implementation details.
This article introduces ClickHouse, an open‑source columnar OLAP database, explains its architecture—including columnar storage, block processing, LSM, indexing and vectorized execution—highlights its performance advantages over other engines, and discusses its limitations such as write‑amplification, concurrency constraints, and ZooKeeper dependency.
This guide explains MariaDB ColumnStore’s columnar architecture, key advantages, step‑by‑step installation, field and SQL limitations, how to migrate InnoDB data, configure multi‑source replication, compare performance with InnoDB, and achieve high availability and dynamic scaling for analytical workloads.
This article examines the trade‑offs of using Flink versus Doris/StarRocks for real‑time data pipelines, highlighting Flink's strengths and pain points, and proposes shifting computation to the OLAP layer with Doris to reduce development and operational costs while maintaining near‑real‑time performance.