Listing write steps for Core and Enterprise

content/influxdb3/core/reference/influxDB3 internals /_index.md

@@ -0,0 +1,16 @@
+---
+title: {{% product-name %}} Internals
+description: >
+  Learn about {{% product-name %}} internal systems and mechanisms.
+menu:
+  influxdb3_core:
+    name: Core internals
+    parent: Reference
+weight: 107
+source: /shared/influxdb3-internals-reference/_index.md
+---
+
+<!--
+The content for this page is at
+// SOURCE /content/shared/influxdb3-internals-reference/_index.md
+->

content/influxdb3/core/reference/influxDB3 internals /data durability/_index.md

@@ -0,0 +1,17 @@
+---
+title: InfluxDB 3 Data durability
+list_title: Data durability
+description: >
+  The `influxdb3` CLI runs and interacts with the InfluxDB 3 Core server.
+menu:
+  influxdb3_core:
+    parent: Core internals
+    name: Data durability
+weight: 200
+source: /shared/influxdb3-internals-reference/durability.md
+---
+
+<!--
+The content for this page is at
+// SOURCE /content/shared/influxdb3-internals-reference/durability.md
+->

content/shared/influxdb3-internals-reference/_index.md

@@ -0,0 +1,3 @@
+### [Data Durability](./durability.md)
+
+{{< children >}}

content/shared/influxdb3-internals-reference/durability.md

@@ -0,0 +1,78 @@
+## How Data Flows Through InfluxDB 3
+
+When data is written to {{% product-name %}}, it progresses through multiple stages to ensure durability, optimize performance, and enable efficient querying. Configuration options at each stage affect system behavior, balancing reliability and resource usage.
+
+### Write Path Overview
+
+{{% product-name %}} processes data through several stages to ensure durability, query performance, and efficient storage. Below is a high-level overview of these stages:
+
+1. [Write validation](#write-validation)
+
+2. [Memory buffer](#memory-buffer) 
+
+3. [Write-Ahead Log (WAL) persistence](#wal-persistence)
+
+4. [Queryable buffer](#query-availability) 
+
+5. [Parquet storage](#parquet-storage) 
+
+6. [In-memory cache](#in-memory-cache) 
+
+
+##### Write Validation
+
+- Process: InfluxDB validates incoming data before accepting it into the system.
+
+- Impact: Prevents malformed or unsupported data from entering the database.
+
+##### Memory Buffer
+
+- Process: Incoming writes are stored in an in-memory buffer before persistence.
+
+- Impact: Increases ingestion efficiency by allowing batch processing.
+
+- Tradeoff: Larger batches improve throughput but require more memory.
+
+##### WAL Persistence
+
+- Process: The write buffer is flushed to the WAL every second (default).
+
+- Impact: Ensures durability by persisting data to object storage.
+
+- Tradeoff: More frequent flushing improves durability but increases I/O overhead.
+
+##### Query Availability
+
+- Process: After WAL persistence, data moves to the queryable buffer.
+
+- Impact: Enables fast queries on recent data.
+
+- Tradeoff: A larger buffer speeds up queries but increases memory usage.
+
+##### Parquet Storage
+
+- Process: Every ten minutes (default), data is persisted to Parquet files in object storage.
+
+- Impact: Provides durable, long-term storage.
+
+- Tradeoff: More frequent persistence reduces reliance on the WAL but increases I/O costs.
+
+##### In-Memory Cache
+
+- Process: Recently persisted Parquet files are cached in memory.
+
+- Impact: Reduces query latency by minimizing object storage access.
+
+## Data flow
+
+As data moves through InfluxDB 3, it follows a structured path to ensure durability, efficient querying, and optimized storage. 
+
+The figure below shows how written data flows through the database.
+
+{{< img-hd src="/img/influxdb/influxdb-3-write-path.png" alt="Write Path for InfluxDB 3 Core & Enterprise" />}}
+
+1. **Incoming writes**: The system validates incoming data and stores it in the write buffer (in memory). If [`no_sync=true`](#no-sync-write-option), the server sends a response to acknowledge the write.
+2. **WAL flush**: Every second (default), the system flushes the write buffer to the Write-Ahead Log (WAL) for persistence in the Object store. If [`no_sync=false`](#no-sync-write-option) (default), the server sends a response to acknowledge the write.
+3. **Query availability**: After WAL persistence completes, data moves to the queryable buffer where it becomes available for queries. By default, the server keeps up to 900 WAL files (15 minutes of data) buffered.
+4. **Long-term storage in Parquet**: Every ten minutes (default), the system persists the oldest data from the queryable buffer to the Object store in Parquet format. InfluxDB keeps the remaining data (the most recent 5 minutes) in memory.
+5. **In-memory cache**: InfluxDB puts Parquet files into an in-memory cache so that queries against the most recently persisted data don't have to go to object storage.

content/shared/v3-core-get-started/_index.md

@@ -376,17 +376,7 @@ The response is the following:
 InfluxDB rejects all points in the batch.
 The response is an HTTP error (`400`) status, and the response body contains `parsing failed for write_lp endpoint` and details about the problem line.
 
-### Data flow
-
-The figure below shows how written data flows through the database.
-
-{{< img-hd src="/img/influxdb/influxdb-3-write-path.png" alt="Write Path for InfluxDB 3 Core & Enterprise" />}}
-
-1. **Incoming writes**: The system validates incoming data and stores it in the write buffer (in memory). If [`no_sync=true`](#no-sync-write-option), the server sends a response to acknowledge the write.
-2. **WAL flush**: Every second (default), the system flushes the write buffer to the Write-Ahead Log (WAL) for persistence in the Object store. If [`no_sync=false`](#no-sync-write-option) (default), the server sends a response to acknowledge the write.
-3. **Query availability**: After WAL persistence completes, data moves to the queryable buffer where it becomes available for queries. By default, the server keeps up to 900 WAL files (15 minutes of data) buffered.
-4. **Long-term storage in Parquet**: Every ten minutes (default), the system persists the oldest data from the queryable buffer to the Object store in Parquet format. InfluxDB keeps the remaining data (the most recent 5 minutes) in memory.
-5. **In-memory cache**: InfluxDB puts Parquet files into an in-memory cache so that queries against the most recently persisted data don't have to go to object storage.
+For more information on data durability see [Data Durability](/influxdb3/version/reference/internals/durability/).
 
 #### Write responses