This is an automated email from the ASF dual-hosted git repository.
lixiaojie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dubbo-website.git
The following commit(s) were added to refs/heads/master by this push:
new 5bc58d5 Update requirements.md (#406)
5bc58d5 is described below
commit 5bc58d5627b4fa0194b624343bf094c723a9331f
Author: 0oneo <neoma...@gmail.com>
AuthorDate: Tue Jun 18 07:53:20 2019 +0800
Update requirements.md (#406)
fix typo
---
docs/en-us/user/preface/requirements.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/en-us/user/preface/requirements.md
b/docs/en-us/user/preface/requirements.md
index 198e917..1695988 100644
--- a/docs/en-us/user/preface/requirements.md
+++ b/docs/en-us/user/preface/requirements.md
@@ -2,7 +2,7 @@
-Before the advent of large-scare services, an application might just exposes
or references remote service by using RMI or Hessian, the call is done by
configuring serive URL, and load balance is done through hardwares, like F5.
+Before the advent of large-scare services, an application might just exposes
or references remote service by using RMI or Hessian, the call is done by
configuring service URL, and load balance is done through hardwares, like F5.
**When there are more and more services, it becomes very difficult to
configure the service URL, the single point pressure of F5 hardware load
balancer is also increasing.** At this point, a service registry is needed to
dynamically register and discover services to make the service's location
transparent. By obtaining the list of service provider addresses in the
consumer side, the soft load balancing and Failover can be realized, this
reduces the dependence on the F5 hardware load bala [...]
