This is an automated email from the ASF dual-hosted git repository.
shetland pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/master by this push:
new d02d2d9 Design/architecture doc touchups (#11762)
d02d2d9 is described below
commit d02d2d9d56f668b9d45c51be4360ad0822fe4710
Author: sthetland <[email protected]>
AuthorDate: Mon Oct 4 11:09:35 2021 -0700
Design/architecture doc touchups (#11762)
* rearrange design content
* casing consistency
Co-authored-by: Charles Smith <[email protected]>
---
docs/assets/services-overview.png | Bin 0 -> 112702 bytes
docs/design/architecture.md | 42 +++++++++++++++++++++++---------------
2 files changed, 25 insertions(+), 17 deletions(-)
diff --git a/docs/assets/services-overview.png
b/docs/assets/services-overview.png
new file mode 100644
index 0000000..157ce60
Binary files /dev/null and b/docs/assets/services-overview.png differ
diff --git a/docs/design/architecture.md b/docs/design/architecture.md
index f10557a..ee3fea1 100644
--- a/docs/design/architecture.md
+++ b/docs/design/architecture.md
@@ -23,22 +23,35 @@ title: "Design"
-->
-Druid has a multi-process, distributed architecture that is designed to be
cloud-friendly and easy to operate. Each
-Druid process type can be configured and scaled independently, giving you
maximum flexibility over your cluster. This
-design also provides enhanced fault tolerance: an outage of one component will
not immediately affect other components.
+Druid has a distributed architecture that is designed to be cloud-friendly and
easy to operate. You can configure and scale services independently so you have
maximum flexibility over cluster operations. This design includes enhanced
fault tolerance: an outage of one component does not immediately affect other
components.
-## Processes and Servers
+## Druid architecture
-Druid has several process types, briefly described below:
+The following diagram shows the services that make up the Druid architecture,
how they are typically organized into servers, and how queries and data flow
through this architecture.
-* [**Coordinator**](../design/coordinator.md) processes manage data
availability on the cluster.
-* [**Overlord**](../design/overlord.md) processes control the assignment of
data ingestion workloads.
-* [**Broker**](../design/broker.md) processes handle queries from external
clients.
-* [**Router**](../design/router.md) processes are optional; they route
requests to Brokers, Coordinators, and Overlords.
-* [**Historical**](../design/historical.md) processes store queryable data.
-* [**MiddleManager**](../design/middlemanager.md) processes ingest data.
+<img src="../assets/druid-architecture.png" width="800"/>
+
+The following sections describe the components of this architecture.
+
+## Druid services
+
+Druid has several types of services:
+
+* [**Coordinator**](../design/coordinator.md) service manages data
availability on the cluster.
+* [**Overlord**](../design/overlord.md) service controls the assignment of
data ingestion workloads.
+* [**Broker**](../design/broker.md) handles queries from external clients.
+* [**Router**](../design/router.md) services are optional; they route requests
to Brokers, Coordinators, and Overlords.
+* [**Historical**](../design/historical.md) services store queryable data.
+* [**MiddleManager**](../design/middlemanager.md) services ingest data.
+
+You can view services in the **Services** tab in the Druid console:
-Druid processes can be deployed any way you like, but for ease of deployment
we suggest organizing them into three server types: Master, Query, and Data.
+
+
+
+## Druid servers
+
+Druid services can be deployed any way you like, but for ease of deployment we
suggest organizing them into three server types: Master, Query, and Data.
* **Master**: Runs Coordinator and Overlord processes, manages data
availability and ingestion.
* **Query**: Runs Broker and optional Router processes, handles queries from
external clients.
@@ -83,11 +96,6 @@ Used for internal service discovery, coordination, and
leader election.
For more details, please see the [ZooKeeper](../dependencies/zookeeper.md)
page.
-## Architecture diagram
-
-The following diagram shows how queries and data flow through this
architecture, using the suggested Master/Query/Data server organization:
-
-<img src="../assets/druid-architecture.png" width="800"/>
## Storage design
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
