The Relay Proxy provides performance and resilience improvements for all server-side SDKs and for SDKs configured to poll. The LaunchDarkly client-side and server-side SDKs you use also impact whether you should use the Relay Proxy. Determining if your configuration is a good use case for the Relay ProxyĪdding the Relay Proxy to your LaunchDarkly configuration introduces architectural complexity that may not be necessary for smaller deployments. Some customers may find operating the Relay Proxy cost-prohibitive for their use case, especially customers on Pro or Starter plans.
Here are some common use cases for the Relay Proxy:
If you don't meet those requirements, using the Relay Proxy is optional. We recommend using the Relay Proxy if you have certain specific configuration requirements, which are explained below. There's also a Docker image on Docker Hub. The full source is in a GitHub repository. The Relay Proxy is an open-source project supported by LaunchDarkly. You can configure the Relay Proxy to carry multiple environment streams from multiple projects. Each of your servers connects only to the Relay Proxy, and the Relay Proxy maintains the connection to LaunchDarkly. The Relay Proxy lets multiple servers connect to a local stream instead of making a large number of outbound connections to LaunchDarkly's streaming service ( ). The Relay Proxy is a small Go application that connects to the LaunchDarkly streaming API and proxies that connection to clients within an organization's network.
#OPEN PROXIE HOW TO#
This topic explains what the Relay Proxy is and how to use it. Read time: 4 minutes Last edited: Overview
0 kommentar(er)
