Remove distributed-data-architecture.md and omit mentions to it (#17097)

docs/glossary.md

@@ -53,8 +53,6 @@ Use the alphabatized list below to find the answer to your single-term questions
 
 - [**Dimension**](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md#dimensions): A dimension is a value that gets shown on a chart.
 
-- [**Distributed Architecture**](https://github.com/netdata/netdata/blob/master/docs/store/distributed-data-architecture.md): The data architecture mindset with which Netdata was built, where all data are collected and stored on the edge, whenever it's possible, creating countless benefits.
-
 ## E
 
 - [**External Plugins**](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md): These gather metrics from external processes, such as a webserver or database, and run as independent processes that communicate with the Netdata daemon via pipes.

docs/metrics-storage-management/enable-streaming.md

@@ -10,9 +10,7 @@ When one node streams metrics to another, the node receiving metrics can visuali
 [export](https://github.com/netdata/netdata/blob/master/docs/export/external-databases.md) all metrics to an external TSDB. When Netdata streams metrics to another
 Netdata, the receiving one is able to perform everything a Netdata instance is capable of.
 
-Streaming lets you decide exactly how you want to store and maintain metrics data. While we believe Netdata's
-[distributed architecture](https://github.com/netdata/netdata/blob/master/docs/store/distributed-data-architecture.md) is 
-ideal for speed and scale, streaming provides centralization options and high data availability.
+Streaming lets you decide exactly how you want to store and maintain metrics data. While we believe Netdata's distributed architecture is ideal for speed and scale, streaming provides centralization options and high data availability.
 
 This document will get you started quickly with streaming. More advanced concepts and suggested production deployments
 can be found in the [streaming and replication reference](https://github.com/netdata/netdata/blob/master/src/streaming/README.md).

docs/quickstart/infrastructure.md

@@ -10,7 +10,7 @@ nodes running the Netdata Agent. A node is any system in your infrastructure tha
 physical or virtual machine (VM), container, cloud deployment, or edge/IoT device.
 
 The Netdata Agent uses zero-configuration collectors to gather metrics from every application and container instantly,
-and uses Netdata's [distributed data architecture](https://github.com/netdata/netdata/blob/master/docs/store/distributed-data-architecture.md) to store metrics
+and uses Netdata's distributed data architecture to store metrics
 locally. Without a slow and troublesome centralized data lake for your infrastructure's metrics, you reduce the
 resources you need to invest in, and the complexity of, monitoring your infrastructure.
 

docs/store/distributed-data-architecture.md

@@ -1,75 +0,0 @@
-# Distributed data architecture
-
-Learn how Netdata's distributed data architecture enables us to store metrics on the edge nodes for security, high performance and scalability.
-
-This way, it helps you collect and store per-second metrics from any number of nodes.
-Every node in your infrastructure, whether it's one or a thousand, stores the metrics it collects.
-
-Netdata Cloud bridges the gap between many distributed databases by _centralizing the interface_ you use to query and
-visualize your nodes' metrics. When you [look at charts in Netdata Cloud](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md)
-, the metrics values are queried directly from that node's database and securely streamed to Netdata Cloud, which
-proxies them to your browser.
-
-Netdata's distributed data architecture has a number of benefits:
-
-- **Performance**: Every query to a node's database takes only a few milliseconds to complete for responsiveness when
-  viewing dashboards or using features
-  like [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/metric-correlations.md).
-- **Scalability**: As your infrastructure scales, install the Netdata Agent on every new node to immediately add it to
-  your monitoring solution without adding cost or complexity.
-- **1-second granularity**: Without an expensive centralized data lake, you can store all of your nodes' per-second
-  metrics, for any period of time, while keeping costs down.
-- **No filtering or selecting of metrics**: Because Netdata's distributed data architecture allows you to store all
-  metrics, you don't have to configure which metrics you retain. Keep everything for full visibility during
-  troubleshooting and root cause analysis.
-- **Easy maintenance**: There is no centralized data lake to purchase, allocate, monitor, and update, removing
-  complexity from your monitoring infrastructure.
-
-## Ephemerality of metrics
-
-The ephemerality of metrics plays an important role in retention. In environments where metrics collection is dynamic and
-new metrics are constantly being generated, we are interested about 2 parameters:
-
-1. The **expected concurrent number of metrics** as an average for the lifetime of the database. This affects mainly the
-   storage requirements.
-
-2. The **expected total number of unique metrics** for the lifetime of the database. This affects mainly the memory
-   requirements for having all these metrics indexed and available to be queried.
-
-## Granularity of metrics
-
-The granularity of metrics (the frequency they are collected and stored, i.e. their resolution) is significantly
-affecting retention.
-
-Lowering the granularity from per second to every two seconds, will double their retention and half the CPU requirements
-of the Netdata Agent, without affecting disk space or memory requirements.
-
-## Long-term metrics storage with Netdata
-
-Any node running the Netdata Agent can store long-term metrics for any retention period, given you allocate the
-appropriate amount of RAM and disk space.
-
-Read our document on changing [how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md) on your nodes for
-details.
-
-You can also stream between nodes using [streaming](https://github.com/netdata/netdata/blob/master/src/streaming/README.md), allowing to replicate databases and create
-your own centralized data lake of metrics, if you choose to do so.
-
-While a distributed data architecture is the default when monitoring infrastructure with Netdata, you can also configure
-its behavior based on your needs or the type of infrastructure you manage.
-
-To archive metrics to an external time-series database, such as InfluxDB, Graphite, OpenTSDB, Elasticsearch,
-TimescaleDB, and many others, see details on [integrating Netdata via exporting](https://github.com/netdata/netdata/blob/master/docs/export/external-databases.md).
-
-When you use the database engine to store your metrics, you can always perform a quick backup of a node's
-`/var/cache/netdata/dbengine/` folder using the tool of your choice.
-
-## Does Netdata Cloud store my metrics?
-
-Netdata Cloud does not store metric values.
-
-To enable certain features, such as [viewing active alerts](https://github.com/netdata/netdata/blob/master/docs/monitor/view-active-alerts.md)
-or [filtering by hostname](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/node-filter.md), Netdata Cloud does
-store configured alerts, their status, and a list of active collectors.
-
-Netdata does not and never will sell your personal data or data about your deployment.