API Call Quotas

Started by deanwebb, October 13, 2017, 08:43:53 AM

Previous topic - Next topic

deanwebb

Ran up against this one yesterday, let me set up the use case...

Organization purchases a product to administer software on a class of devices, we'll call the product BYODMon. Another product is doing software audits, to make sure required software is installed, has a valid license, and has a valid user logged in, we'll call that product AuditStuff.

Every time AuditStuff checks for BYODMon, it generates an API call to the BYODMon central server, which resides in the cloud. BYODMon is configured to get 10,000 API calls per day, but the AuditStuff checks happen every time a device registers on the network, which is all through the day as the devices reconnect after waking up. AuditStuff sends 30,000 calls per day and the BYODMon admins are getting pinged on license terms, organization has to cut back the API calls or buy bigger capacity.

Solution for cutting back is to reduce frequency of AuditStuff checks, which takes a bit of engineering.

I would imagine a similar solution could emerge for other cloud-managed platforms. Cloud being cheaper may be because your organization no longer has the all-you-can-eat aspect of local storage/apps.
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

icecream-guy

you are in business,  you pay up for the license and pass the costs on to your customers.
:professorcat:

My Moral Fibers have been cut.