From 038efe1526eee5cd8fda33cd1cfe7e375250aa96 Mon Sep 17 00:00:00 2001
From: javahongxi <javahongxi@qq.com>
Date: Sun, 9 Jun 2019 10:06:19 +0800
Subject: [PATCH] =?UTF-8?q?ES=E4=BB=A3=E6=9B=BF=E5=85=B3=E7=B3=BB=E5=9E=8B?=
 =?UTF-8?q?=E6=95=B0=E6=8D=AE=E5=BA=93=E8=AF=BB=E5=86=99=E5=88=86=E7=A6=BB?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 whatsmars-elasticsearch/README.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/whatsmars-elasticsearch/README.md b/whatsmars-elasticsearch/README.md
index 649bd532..296d2053 100644
--- a/whatsmars-elasticsearch/README.md
+++ b/whatsmars-elasticsearch/README.md
@@ -1 +1,6 @@
-https://www.elastic.co/cn/downloads/past-releases/elasticsearch-6-4-3
\ No newline at end of file
+https://www.elastic.co/cn/downloads/past-releases/elasticsearch-6-4-3
+
+对于关系型数据库，当读请求数远大于写请求数时，读请求会影响写请求的性能，此时我们常用的做法是读写分离。
+数据库读写分离操作简单，但遇到跨表甚至跨库查询时，会受到分布式数据库中间件支持能力的限制。此时应考虑
+通过数据库同步组件将数据异构到搜索引擎如ES，对于实时性要求不高和那些复杂的查询直接走ES，其他少部分请求
+则可以走关系型数据库，这种情况下完全不用再做关系型数据库读写分离。
\ No newline at end of file
-- 
GitLab