From 6697d749fedee73b2b2a68b5a43a42fb1c436c52 Mon Sep 17 00:00:00 2001 From: Johan Haals Date: Tue, 3 Jan 2023 15:34:45 +0100 Subject: [PATCH] Update scaling docs Signed-off-by: Johan Haals --- docs/deployment/scaling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/deployment/scaling.md b/docs/deployment/scaling.md index f3aa744cf7..f41708f32f 100644 --- a/docs/deployment/scaling.md +++ b/docs/deployment/scaling.md @@ -17,7 +17,7 @@ into multiple different services, each running a different set of plugins. This is a more advanced approach and requires you to be able to route requests to the appropriate backends based on the plugin ID. Both for ingress, but also internal traffic between Backstage backends, which is done by creating a custom -implementation of the [PluginEndpointDiscover](../reference/backend-common.pluginendpointdiscovery.md) interface. +implementation of the [DiscoveryService](../reference/backend-plugin-api.discoveryservice.md) interface. Lastly, you can also replicate the Backstage deployments across multiple regions. This is not a pattern that there is built-in support for and typically only makes