From 7ac467c33591f09d64e26e49b9e5f5382a0107c7 Mon Sep 17 00:00:00 2001 From: fengdongdong02 Date: Thu, 28 Jul 2016 20:18:50 +0800 Subject: [PATCH] translate 410_Scaling/10_Intro --- 410_Scaling/10_Intro.md | 30 ++++++------------------------ 1 file changed, 6 insertions(+), 24 deletions(-) diff --git a/410_Scaling/10_Intro.md b/410_Scaling/10_Intro.md index fc4d8ec..1996df2 100755 --- a/410_Scaling/10_Intro.md +++ b/410_Scaling/10_Intro.md @@ -1,29 +1,11 @@ -[[scale]] -== Designing for Scale +## 可扩展性规划 -Elasticsearch is used by some companies to index ((("scaling", "designing for scale")))and search petabytes of data -every day, but most of us start out with something a little more humble in -size. Even if we aspire to be the next Facebook, it is unlikely that our bank -balance matches our aspirations. We need to build for what we have today, but -in a way that will allow us to scale out flexibly and rapidly. +在某些公司Elasticsearch被用来每天索引和检索PB级别的数据，但大多情况我们是从一个相对小很多的数据集开始系统建设的。虽然我们希望能成为下一个Facebook，但是现实往往比理想更骨感。虽然我们从当下开始建设，但之后横向扩展的灵活性和简便性还是必须考虑的。 -Elasticsearch is built to scale. It will run very happily on your laptop or -in a cluster containing hundreds of nodes, and the experience is almost -identical. Growing from a small cluster to a large cluster is almost entirely -automatic and painless. Growing from a large cluster to a very large cluster -requires a bit more planning and design, but it is still relatively painless. +ELasticsearch天生就是可扩展的。无论是运行在你的个人电脑之上还是运行在由数百个节点构成的集群之上，ELasticsearch都能很好的工作而且两者之间的使用体验并不会有太大的差异。从一个小集群扩展到一个大集群的过程几乎是自动化的、自然而然的。从一个大集群扩展到一个巨型集群会需要一点规划与设计，但是相对来说还是比较自然的。 -Of course, it is not magic. Elasticsearch has its limitations too. If you -are aware of those limitations and work with them, the growing process will be -pleasant. If you treat Elasticsearch badly, you could be in for a world of -pain. +当然，Elasticsearch也不是包治百病的灵丹妙药，它也有自身的限制。如果你了解这些限制并且能很好的规避它们，这个扩展的过程将会比较平顺。否则你不善待Elasticsearch，它也不会让你很舒服。 -The default settings in Elasticsearch will take you a long way, but to get the -most bang for your buck, you need to think about how data flows through your -system. We will talk about two common data flows: time-based data (such as log -events or social network streams, where relevance is driven by recency), and -user-based data (where a large document collection can be subdivided by user or -customer). +Elasticsearch的默认设置足以支撑你的系统走很长的路，但是为了更好的利用资源，你还是要认真的设计系统中的数据流。我们将会讨论两个通用的数据流场景：基于时间的数据流（比如事件日志、社交网络时间轴这些基于时间相关性的数据）和基于用户的数据流（比如大规模的数据集合可以按照用户/客户进行切分的场景）。 -This chapter will help you make the right decisions up front, to avoid -nasty surprises later. +本章我们将帮助在系统建设早期做出正确的决策，从而尽可能避免日后意想不到的麻烦。