In API Manager 3.0.0 we plan to change the label "Tiers" to "Business Plans". I believe its the impression that matters the most in this case. And we can also change the default business plans to have a mix of hard and soft plans. A hard plan will drop requests after reaching quota, a soft plan will record the excess but still allow requests to pass-through even after the quota is fulfilled.
Regarding implementing actual invoicing and billing capabilities, I haven't personally been a fan of doing it from the product itself because billing in itself is a complicated domain. When it comes to issuing discounts, seasonal offers, etc, building a product that does all that becomes a complex task. Building a solution that doesn't offer enough billing capabilities is also not good. So we either have to go all out on this or not do it at all. On Tue, Jul 18, 2017 at 1:21 PM, Chintana Wilamuna <[email protected]> wrote: > Hi, > > Right now API Manager billing is tightly coupled to the throttling > policies. Sometimes this is a confusion to end users. From a product > architecture PoV one can argue that these components should be separate. > > Alternatively we can propose our current throttling screen to say API > Contract? Then, actually throttling and billing falls nicely into the > contract you define and throttling and billing is part of that. > > Another point is that, from API Manager product PoV there's no where to > define an actual billing plan. May be we can introduce ability for a > publisher/admin to define a billing plan for APIs and potentially use > analytics to push those to an actual billing engine via a data publisher? > > -Chintana > > -- > Chintana Wilamuna | Associate Director/Solutions Architect | WSO2 > <http://wso2.com/> Inc. > 408 429 3321 <(408)%20429-3321> | http://engwar.com/ > > -- Nuwan Dias Software Architect - WSO2, Inc. http://wso2.com email : [email protected] Phone : +94 777 775 729
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
