From ad45a94ab7b8a199a74bdcbdb3226cbb705bafd6 Mon Sep 17 00:00:00 2001 From: yuyujulin Date: Wed, 18 Sep 2019 15:09:51 +0800 Subject: [PATCH] correct a typo (#3483) --- docs/en/FAQ/why_mq_not_involved.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/FAQ/why_mq_not_involved.md b/docs/en/FAQ/why_mq_not_involved.md index 2cf7c53154..b20b797651 100644 --- a/docs/en/FAQ/why_mq_not_involved.md +++ b/docs/en/FAQ/why_mq_not_involved.md @@ -6,7 +6,7 @@ They think MQ should be better in the performance and supporting high throughput Here are the reasons the SkyWalking's opinions. -### Is MQ a good or right way to community with OAP backend? +### Is MQ a good or right way to communicate with OAP backend? This question comes out when people think about what happens when the OAP cluster is not powerful enough or offline. But I want to ask the questions before answer this. 1. Why do you think OAP should be not powerful enough? As it is not, the speed of data analysis wouldn't catch up with producers(agents). Then what is the point of adding new deployment requirement? -- GitLab