Great APIs need a plan! by: Robert Wunderlich
January 13, 2019 Leave a comment
We recently released API Platform Cloud service 18.1.5 and with that we are introducing phase 1 of plans! To be fully transparent, we’ve had plans built into the service from day 1, but this marks a step in making the feature available.
What are plans you may ask?
Plans provide the measured access to one or more APIs serving as the foundation for monetization.
Plans define limits at the subscriber level that stretches across APIs.
To explain this further, let’s use the example of a rate-limit. A rate limit controls the number of calls within a certain time period. The API Rate Limit protects a system by limiting the number of calls that may be made to a particular API, no matter who is calling the API. For example, if my back-end system can handle no more than 10000 requests per second, I may set an API Rate Limit of 10000 per second which would apply for all callers.
Another limit is the Application Rate Limit, which we can call the "fair share" limit. This stipulates that no one application can get more than a limited number of calls within a certain time period. For example, I may decide that no one application can get more than 1000 calls per second. If I have 5 applications subscribed then this means that there can be a total of 5000 requests per second.
Plans takes this forward in a much richer way in that I can set limits for the consumer. With plans, the API consumer now subscribes to the plan and APIs are entitled to that plan. When a consumer subscribes to the plan, the consumer gets access to all of the APIs entitled in the plan. Read the complete article here.
For regular information on Oracle PaaS become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
Blog
Twitter
LinkedIn
Facebook
Wiki
Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress