From 6febe94113796339e67ad228fe0c8cf4f7bb344f Mon Sep 17 00:00:00 2001 From: Pandey Anshuman Kishore Date: Sat, 8 Feb 2025 02:12:37 +0530 Subject: [PATCH 1/2] Fix gRPC API link The link to gRPC API was broken, leading to 404 error. --- docs/03-concepts/05-topology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/03-concepts/05-topology.md b/docs/03-concepts/05-topology.md index 1f1ba86e4..a94875e85 100644 --- a/docs/03-concepts/05-topology.md +++ b/docs/03-concepts/05-topology.md @@ -18,7 +18,7 @@ Note that both types of :worker:workers: as well as external clients are roles a ![Cadence Architecture](https://user-images.githubusercontent.com/14902200/160308507-2854a98a-0582-4748-87e4-e0695d3b6e86.jpg) -At the core of Cadence is a highly scalable multitenant service. The service exposes all of its functionality through a strongly typed [gRPC API](https://github.com/cadence-workflow/cadence-idl/tree/master/proto/cadence-workflow/cadence/api/v1). A Cadence cluster include multiple services, each of which may run on multiple nodes for scalability and reliablity: +At the core of Cadence is a highly scalable multitenant service. The service exposes all of its functionality through a strongly typed [gRPC API](https://github.com/cadence-workflow/cadence-idl/tree/master/go/proto/api/v1). A Cadence cluster include multiple services, each of which may run on multiple nodes for scalability and reliablity: - Front End: which is a stateless service used to handle incoming requests from Workers. It is expected that an external load balancing mechanism is used to distribute load between Front End instances. - History Service: where the core logic of orchestrating workflow steps and activities is implemented - Matching Service: matches workflow/activity tasks that need to be executed to workflow/activity workers that are able to execute them. Matching is assigned task for execution by the history service From 7527615036289aeadca7a3e921c24feb1c4595bf Mon Sep 17 00:00:00 2001 From: Pandey Anshuman Kishore Date: Tue, 11 Feb 2025 17:59:52 +0100 Subject: [PATCH 2/2] Update the reference URL Co-authored-by: Adhitya Mamallan --- docs/03-concepts/05-topology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/03-concepts/05-topology.md b/docs/03-concepts/05-topology.md index a94875e85..104cef7c1 100644 --- a/docs/03-concepts/05-topology.md +++ b/docs/03-concepts/05-topology.md @@ -18,7 +18,7 @@ Note that both types of :worker:workers: as well as external clients are roles a ![Cadence Architecture](https://user-images.githubusercontent.com/14902200/160308507-2854a98a-0582-4748-87e4-e0695d3b6e86.jpg) -At the core of Cadence is a highly scalable multitenant service. The service exposes all of its functionality through a strongly typed [gRPC API](https://github.com/cadence-workflow/cadence-idl/tree/master/go/proto/api/v1). A Cadence cluster include multiple services, each of which may run on multiple nodes for scalability and reliablity: +At the core of Cadence is a highly scalable multitenant service. The service exposes all of its functionality through a strongly typed [gRPC API](https://github.com/cadence-workflow/cadence-idl/tree/master/proto/uber/cadence/api/v1). A Cadence cluster include multiple services, each of which may run on multiple nodes for scalability and reliablity: - Front End: which is a stateless service used to handle incoming requests from Workers. It is expected that an external load balancing mechanism is used to distribute load between Front End instances. - History Service: where the core logic of orchestrating workflow steps and activities is implemented - Matching Service: matches workflow/activity tasks that need to be executed to workflow/activity workers that are able to execute them. Matching is assigned task for execution by the history service