This is an automated email from the ASF dual-hosted git repository. yukon pushed a commit to branch zhouxinyu-patch-1 in repository https://gitbox.apache.org/repos/asf/rocketmq-site.git
commit af60d7c84c3bd6d1d82f2e967085a1de084bca6f Author: yukon <[email protected]> AuthorDate: Sat Apr 1 19:46:17 2023 +0800 Polishing the whychoose.md doc --- .../version-5.0/01-introduction/01whychoose.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/i18n/en/docusaurus-plugin-content-docs/version-5.0/01-introduction/01whychoose.md b/i18n/en/docusaurus-plugin-content-docs/version-5.0/01-introduction/01whychoose.md index 45ae646a5..89767acb3 100644 --- a/i18n/en/docusaurus-plugin-content-docs/version-5.0/01-introduction/01whychoose.md +++ b/i18n/en/docusaurus-plugin-content-docs/version-5.0/01-introduction/01whychoose.md @@ -5,11 +5,11 @@ slug: / # Why choose RocketMQ ## Why RocketMQ -During Ali's nascent days of RocketMQ, we used it for asynchronous communications, search, social networking activity flows, data pipelines, and trade processes. As our trade business throughput rose, the pressure originating from our messaging cluster became urgent. +During the early stages of RocketMQ's development at Alibaba, we utilized it for a multitude of purposes, including asynchronous communications, search, social networking activity flows, data pipelines, and trade processes. As our trade business grew, we noticed that the messaging cluster was under increasing pressure. -According to our observation and analysis, the ActiveMQ IO module reaches a bottleneck as the number of queues and virtual topics increases. We tried our best to mitigate this problem by way of throttling, circuit breaker, or service downgrading, but none of them was satisfying. Alternatively, we tried the popular messaging solution: Kafka. Unfortunately, Kafka could not meet our requirements, especially in terms of low latency and high reliability, as detailed below. In this case, we de [...] +After observing and analyzing the performance of the ActiveMQ IO module, we identified a bottleneck as the number of queues and virtual topics increased. We attempted to address this issue through various methods, such as throttling, circuit breakers, and service downgrades, but none proved satisfactory. We also considered using Kafka, a popular messaging solution, but it did not meet our requirements for low latency and high reliability, as explained below. As a result, we made the deci [...] -Since its inception, Apache RocketMQ has been widely adopted by many enterprise developers and cloud vendors for its simple architecture, rich business functionality, and extreme scalability. After more than ten years of large-scale scenario polishing, RocketMQ has become the industry consensus as the preferred solution for financial-grade reliable business messages, and is widely used in business scenarios in Internet, big data, mobile Internet, IoT and other fields. +Since its inception, Apache RocketMQ has been widely adopted by enterprise developers and cloud vendors due to its simple architecture, rich business functionality, and extreme scalability. After more than a decade of extensive scenario polishing, RocketMQ has become the industry standard for financial-grade reliable business messages and is widely used in Internet, big data, mobile Internet, IoT, and other fields. :::tip
