Oracle Integration Cloud: Building Integrations That Survive Production · Module 14 · Performance and throughput
Throttling and back pressure
Lesson 142 of 175 · 3 min
Being a good client of a system that has limits. RATE LIMITING YOURSELF BEFORE IT DOES IT FOR YOU. Most target systems have a limit, whether or not it is published. An API rate limit, a connection pool, a licensed concurrency, or simply a database that degrades under load. Your integration can exceed it, and what happens then is decided by the target rather than by you. THE RESPONSES RANGE FROM POLITE TO CATASTROPHIC. A well-built API answers 429 with a header saying how long to wait — annoying and recoverable. A less well-built one starts timing out. The worst case is a system that does not refuse at all and simply becomes slow for everybody using it, which is your integration degrading a client's production ERP for its own users, and nobody will look at your flow first. SO THE DISCIPLINE IS TO LIMIT YOURSELF DELIBERATELY RATHER THAN DISCOVERING…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.