You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by fj...@apache.org on 2019/11/07 22:26:10 UTC
[incubator-druid-website-src] branch a created (now 9a739bb)
This is an automated email from the ASF dual-hosted git repository.
fjy pushed a change to branch a
in repository https://gitbox.apache.org/repos/asf/incubator-druid-website-src.git.
at 9a739bb some wording updates
This branch includes the following new commits:
new 9a739bb some wording updates
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[incubator-druid-website-src] 01/01: some wording updates
Posted by fj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
fjy pushed a commit to branch a
in repository https://gitbox.apache.org/repos/asf/incubator-druid-website-src.git
commit 9a739bb64ba42f51621379538530f305fda7772d
Author: fjy <fa...@gmail.com>
AuthorDate: Thu Nov 7 14:26:03 2019 -0800
some wording updates
---
_data/featured.yml | 6 ++++++
index.html | 2 +-
technology.md | 16 ++++++++--------
3 files changed, 15 insertions(+), 9 deletions(-)
diff --git a/_data/featured.yml b/_data/featured.yml
index 21a59b1..fd3dd8f 100644
--- a/_data/featured.yml
+++ b/_data/featured.yml
@@ -1,3 +1,9 @@
+ - date: 2019-10-16
+ title: "Druid query view: An elegant SQL interface for a more civilized age"
+ name: "Margaret Brewster"
+ link: https://imply.io/post/druid-console-query-view
+ company: Imply
+
- date: 2019-09-15
title: "Data Retention and Deletion in Apache Druid"
name: "Dana Assa and Itai Yaffe"
diff --git a/index.html b/index.html
index 259dd07..232286d 100644
--- a/index.html
+++ b/index.html
@@ -60,7 +60,7 @@ canonical: 'https://druid.apache.org/'
<span class="fa fa-globe fa"></span>
<h5>Deploy in AWS/GCP/Azure, hybrid clouds, Kubernetes, and bare metal</h5>
<p>
- Druid can be deployed in any *NIX environment on commodity hardware, both in the cloud and on premise. Deploying Druid is easy: scaling up and down is as simple as adding and removing processes.
+ Druid can be deployed in any *NIX environment on commodity hardware, both in the cloud and on premise. Deploying Druid is easy: scaling up and down is as simple as adding and removing Druid services.
</p>
</div>
</div>
diff --git a/technology.md b/technology.md
index f7e64da..984b604 100644
--- a/technology.md
+++ b/technology.md
@@ -129,12 +129,12 @@ For more information, please visit [our docs page](/docs/latest/querying/queryin
## Architecture
Druid has a microservice-based architecture can be thought of as a disassembled database.
-Each core process in Druid (ingestion, querying, and coordination) can be separately or jointly deployed on commodity hardware.
+Each core service in Druid (ingestion, querying, and coordination) can be separately or jointly deployed on commodity hardware.
-Druid explicitly names every main process to allow the operator to fine tune each process based on the use case and workload.
-For example, an operator can dedicate more resources to Druid’s ingestion process while giving less resources to Druid’s query process if the workload requires it.
+Druid explicitly names every main service to allow the operator to fine tune each service based on the use case and workload.
+For example, an operator can dedicate more resources to Druid’s ingestion service while giving less resources to Druid’s query service if the workload requires it.
-Druid processes can independently fail without impacting the operations of other processes.
+Druid services can independently fail without impacting the operations of other services.
<div class="image-large">
<img src="img/diagram-7.png" style="max-width: 620px;">
@@ -157,11 +157,11 @@ As such, Druid possesses several features to ensure uptime and no data loss.
</div>
<div class="feature">
<span class="fa fa-th-large fa"></span>
- <h5>Independent processes</h5>
+ <h5>Independent services</h5>
<p>
- Druid explicitly names all of its main processes and each process can be fine tuned based on use case.
- Processes can independently fail without impacting other processes.
- For example, if the ingestion process fails, no new data is loaded in the system, but existing data remains queryable.
+ Druid explicitly names all of its main services and each service can be fine tuned based on use case.
+ Services can independently fail without impacting other services.
+ For example, if the ingestion services fails, no new data is loaded in the system, but existing data remains queryable.
</p>
</div>
<div class="feature">
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org