Member-only story

Data Layout and Schema Design Best Practices for InfluxDB

Anais Dotis
9 min readSep 15, 2020

--

Figuring out the best data layout for InfluxDB v2 is important in optimizing the resources used by InfluxDB, as well as improving ingestion rates and the performance of queries and tasks. You also want to consider developer and user experience (UX). This post will walk you through developing a schema for an IoT application example and answer the following questions:

  1. What are general recommendations for schema design and data layout for InfluxDB v2?
  2. What impacts computing resources such as memory, CPU, and storage? How do I optimize InfluxDB for the available resources?
  • What is series cardinality?
  • How do I calculate series cardinality?
  • How are series cardinality and ingest rate related?
  • What is downsampling? When should I perform downsampling?

3. How do I reduce my resource usage?

  • How do I optimize my InfluxDB schema for increased query and downsampling performance?

4. What other considerations should I take when designing my InfluxDB schema?

  • How will my organization interact with the data? How does UX design affect schema?
  • How do security and authorization considerations impact my schema design?

5. What are some common schema design mistakes?

TL;DR General recommendations for schema design…

--

--

Anais Dotis
Anais Dotis

Written by Anais Dotis

Developer Advocate at InfluxData

No responses yet