---
title: Best practices for writing data
description: Learn about the recommendations and best practices for writing data to InfluxDB.
url: https://docs.influxdata.com/influxdb/v2/write-data/best-practices/
estimated_tokens: 550
product: InfluxDB OSS v2
version: v2
---

# Best practices for writing data

This page documents an earlier version of InfluxDB OSS. [InfluxDB 3 Core](/influxdb3/core/) is the latest stable version.

#### API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — **capture any plaintext tokens you still need before you upgrade**.

For more information, see [Token hashing](/influxdb/v2/admin/tokens/#token-hashing).

The following articles provide recommendations and best practices for writing data to InfluxDB.

### [Optimize writes to InfluxDB](/influxdb/v2/write-data/best-practices/optimize-writes/)

Simple tips to optimize performance and system overhead when writing data to InfluxDB.

### [Handle duplicate data points](/influxdb/v2/write-data/best-practices/duplicate-points/)

InfluxDB identifies unique data points by their measurement, tag set, and timestamp. This article discusses methods for preserving data from two points with a common measurement, tag set, and timestamp but a different field set.

### [InfluxDB schema design](/influxdb/v2/write-data/best-practices/schema-design/)

Design your schema for simpler and more performant queries.

### [Resolve high series cardinality](/influxdb/v2/write-data/best-practices/resolve-high-cardinality/)

Reduce high series cardinality in InfluxDB. If reads and writes to InfluxDB have started to slow down, you may have high cardinality. Find the source of high cardinality and adjust your schema to resolve high cardinality issues.