Provisioning Paid Plans
Fleeting- Référence externe : https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.13/html/admin_portal_guide/provision-paid-plans
differentiate between the tiers in your pricing model. The tiers can be driven by volume or usage, API functionality, access to other resources, or a combination of them:
- Volume / Usage
- The most common way to differentiate between tiers is based on volume because volume usually has a strong correlation to value to the customer as well as cost to serve. You can apply a global hit count for calls on the product or a more granular measurement at the method level. Volume drivers are applied at the level of the global hits metric, or for individual methods under hits. Multiple pricing rules can be applied to any metric. Note that the hits calculation is cumulated over a one-month billing cycle.
- Functionality
- You can enable or disable access to parts of your product depending on the tier. This is a good approach to distinguish between standard and premium levels.
- Resources
- You can also create tiers based on access to any other resources that provide value to the customer or drive costs in your infrastructure – for example, gigabytes of bandwidth consumed, number of users, or transaction values. Resource drivers are similar to volume drivers but are applied on custom metrics
must decide whether the tiers will be based on a flat rate subscription, a variable rate, or a one-off upfront charge