mirror of
https://github.com/Unleash/unleash.git
synced 2025-01-31 00:16:47 +01:00
fix: adjust the proxy docs
This commit is contained in:
parent
5ba0f3b5f0
commit
5fd38d1644
@ -13,9 +13,9 @@ Which way is right for you will depend on your setup and your needs. In general,
|
||||
If you want Unleash to host the proxy for you, you should be aware of the following limitations:
|
||||
|
||||
- This is only available to Pro and Enterprise customers who have signed up for a managed Unleash instance.
|
||||
- You'll get a total of two (2) proxies: One for the "development" environment and one for the "production" environment.
|
||||
- The proxies _will not_ scale, regardless of how many requests you're getting.
|
||||
- If you go above an average of 10 requests per second, then you'll be charged extra. (Is this pricing available anywhere?)
|
||||
- Pro customers will get a total of two (2) proxies: One for the "development" environment and one for the "production" environment.
|
||||
- We do allow short spikes in traffic and our adaptive infrastructure will automatically scale your needs.
|
||||
- If you go above an average of 10 requests per second, then you'll be charged extra for the hosted proxy.
|
||||
- There's no guarantee that it'll be close to your applications. This means you'll get higher response times.
|
||||
- When we host the proxy, we will also receive whatever end user data you put in the [Unleash context](../user_guide/unleash-context.md). This may or may not be an issue depending on your business requirements.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user