Since Nedap Harmony is a multi-tenant application, there are some limits to avoid the "noisy neighbor" effect where one user takes up so much of the processing power that other users experience degraded performance or even errors.
Well behaving Nedap Harmony API users:
- Send HTTP requests of maximum 4 MB;
- Use a maximum of three concurrent HTTP requests;
- Try to speed up their integration by minimizing the amount of requests and amount of data returned through intelligent use of the request parameters of an API.
Nedap Harmony may or may not actively enforce these limits.
Updated about 1 year ago