This is an automated email from the ASF dual-hosted git repository.

visortelle pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 9437aa4faaad Update usecases.ts (#955)
9437aa4faaad is described below

commit 9437aa4faaad7b8f09c102102c6ba68fe6aff838
Author: Jarrick Van Camp <[email protected]>
AuthorDate: Fri Sep 6 06:21:31 2024 +0200

    Update usecases.ts (#955)
---
 data/usecases.ts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/data/usecases.ts b/data/usecases.ts
index f68a17a9cba2..5564e5f2ae75 100644
--- a/data/usecases.ts
+++ b/data/usecases.ts
@@ -28,7 +28,7 @@ const useCases: UseCase[] = [
     {
         icon: "arrow",
         title: "Scalable RPC",
-        text: "<p>In a micro-services architecture, there is a need to 
communicate between services constantly. One way of doing it is direct API 
calls, which require<ul><li>A service discovery system, which registers new 
instances into a list of available instances for a service</li><li>Load 
balancing system, to load balance calls among the list of 
instances</li><li>Networking rules to define which defines which service can 
access which network</li><li>A central configuration system to  [...]
+        text: "<p>In a micro-services architecture, there is a need to 
communicate between services constantly. One way of doing it is direct API 
calls, which require<ul><li>A service discovery system, which registers new 
instances into a list of available instances for a service</li><li>Load 
balancing system, to load balance calls among the list of 
instances</li><li>Networking rules to define which defines which service can 
access which network</li><li>A central configuration system to  [...]
         smallText: "Scalable RPC, in the context of micro-services, uses 
topics for indirect API communication, simplifying load balancing and 
eliminating traditional networking complexities by using shared topics for each 
service to balance load and individual topics for response reception. This 
approach is highly scalable, efficiently supporting systems with thousands of 
instances.",
         docsLink: "concepts-broker-load-balancing-benefits/#scalability",
         caseLink: false
@@ -43,4 +43,4 @@ const useCases: UseCase[] = [
     },
 ];
 
-export default useCases;
\ No newline at end of file
+export default useCases;

Reply via email to