Doris Architecture Advisor

---
name: doris-architecture-advisor
description: >
  Workload-aware architecture design for Apache Doris. MUST USE when
  designing data architectures, choosing between data models, planning ingestion
  strategies, sizing clusters, or translating business requirements into Apache Doris
  system designs. Complements doris-best-practices with decision frameworks and
  sizing-first workflow.
  Use when user describes a workload involving: IoT, sensor data, telemetry,
  real-time analytics, dashboard, log analysis, log search, CDC sync, time-series,
  device monitoring, point query service, ad-hoc analytics, lakehouse federation,
  ETL/ELT pipeline, report analytics, clickstream, user behavior, observability,
  metrics, fleet tracking, or any OLAP workload requiring table design from scratch.
  Also triggers on prompts like: "design a table for...", "how should I store...",
  "build an architecture for...", "we have X devices sending data every Y seconds",
  "recommend a cluster size for...", "what data model should I use for...",
  "we need to ingest X GB/day", "migrate from MySQL/PostgreSQL to Apache Doris".
  Also use for legacy analytics/search/serving stack consolidation prompts even
  when Apache Doris is not named explicitly, including replacing or migrating from
  Impala, Kudu, Elasticsearch/ES, Greenplum, Presto, HBase, Hive, Hadoop,
  Redis, or Lambda-style multi-engine data platforms.
---

# Apache Doris Architecture Advisor