Cleint limitations

[orbitlens]

We need to implement basic rate-limiting features and max resource policy for clients.
Configuration options:

• Max requests per 5 seconds timespan (e.g., max 10 requests per any 5s timespan).
• Max requests per minute (e.g., no more than 30 requests per minute).
• Max requests per hour (e.g., up to 1000 requests per hour).
• Max open orders - maximum number of outstanding orders on exchanges.
• Withdrawal requests limit per day (for example, no more than 50 withdrawals within any 24h timespan).

[s-a-y]

Requests rate limiting is usually better done by reverse proxy, like nginx or even cloudflare.
Max open orders and withdrawal request limits are the real features here.

[orbitlens]

@s-a-y

Requests rate limiting is usually better done by reverse proxy, like nginx or even cloudflare.
Max open orders and withdrawal request limits are the real features here.

Yep, it's the best option for HTTP or REST in most cases, but

1. We are using WebSockets, and reverse proxy are usually only slow down things with such setups.
2. This project is supposed to be used by different organizations, so we strive to minimize total number of dependencies and avoid third-party vendor locks.
3. Those settings are supposed to be configurable in runtime. If constellation members agree on changing current limits, the system should automatically apply them, which may be problematic with external reverse proxy.
4. Constellation members might want to set custom limits on per-account basis. For example, for market makers, payment systems, or HFT traders. It's one of the potential financial incentives to run a constellation.

Anyways, thanks for your suggestion, your professional opinion is much appreciated as always. Please let me know if you spot any other inconsistencies.

[s-a-y]

Sure, they way you describe it - makes perfect sense.
I haven't initially thought you want control on account-level or system-wide settings.