From 497b9a9e7c5cdcb0b769691ea40a74a4d284cfff Mon Sep 17 00:00:00 2001 From: Mars Wong Date: Tue, 14 Mar 2017 15:03:13 +0800 Subject: [PATCH] docs(faq): fix cluster link (#557) --- docs/source/en/faq.md | 2 +- docs/source/zh-cn/faq.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/en/faq.md b/docs/source/en/faq.md index 05e76d7b92..2ed71608b4 100644 --- a/docs/source/en/faq.md +++ b/docs/source/en/faq.md @@ -13,7 +13,7 @@ When you got some trouble, and want to find out what is the final config using a 1. PM2 itself is too complex to issue problems if any. 2. Deep optimization could be difficlut to achieve if choosing PM2. -3. Pattern like one leader process communicating with remote services, along with serveral follower processes delegating request to it (（[Cluster](./advanced/cluster.md)), is a rigid demand for reducing connections and data exchange load, espeically when facing applications in very large scale. egg originates from Ant Financial Group and Alibaba Group, we start with applications in that scale at first, so we take these goals into consideration. All of these goals above could be hard to achieve with PM2. +3. Pattern like one leader process communicating with remote services, along with serveral follower processes delegating request to it ([Cluster](./core/cluster-and-ipc.md)), is a rigid demand for reducing connections and data exchange load, espeically when facing applications in very large scale. egg originates from Ant Financial Group and Alibaba Group, we start with applications in that scale at first, so we take these goals into consideration. All of these goals above could be hard to achieve with PM2. Process management is very important. It defines the way we write code, meanwhile relates to deep runtime optimizations. So we think it's better included in framework itself. diff --git a/docs/source/zh-cn/faq.md b/docs/source/zh-cn/faq.md index 225ea0aea1..39707edfa7 100644 --- a/docs/source/zh-cn/faq.md +++ b/docs/source/zh-cn/faq.md @@ -15,7 +15,7 @@ title: 常见问题 1. PM2 模块本身复杂度很高，出了问题很难排查。我们认为框架使用的工具复杂度不应该过高，而 PM2 自身的复杂度超越了大部分应用本身。 2. 没法做非常深的优化。 -3. 切实的需求问题，一个进程里跑 leader，其他进程代理到 leader 这种模式（[多进程模型](./advanced/cluster.md)），在企业级开发中对于减少远端连接，降低数据通信压力等都是切实的需求。特别当应用规模大到一定程度，这就会是刚需。egg 本身起源于蚂蚁金服和阿里，我们对标的起点就是大规模企业应用的构建，所以要非常全面。这些特性通过 PM2 很难做到。 +3. 切实的需求问题，一个进程里跑 leader，其他进程代理到 leader 这种模式（[多进程模型](./core/cluster-and-ipc.md)），在企业级开发中对于减少远端连接，降低数据通信压力等都是切实的需求。特别当应用规模大到一定程度，这就会是刚需。egg 本身起源于蚂蚁金服和阿里，我们对标的起点就是大规模企业应用的构建，所以要非常全面。这些特性通过 PM2 很难做到。 进程模型非常重要，会影响到开发模式，运行期间的深度优化等，我们认为可能由框架来控制比较合适。