1. 22
  1.  

  2. 8

    Predictable pricing is a BIG plus for anyone working in a larger organization.

    Bucket pricing also helps with preventing getting a huge bill in case of an infinite loop making an API call and getting charged for it.

    As a user/hobbyist, I like usage-based pricing of course :)

    1. 1

      Bucket pricing also helps with preventing getting a huge bill in case of an infinite loop making an API call and getting charged for it.

      That depends on whether or not money is auto-spent, not whether or not buckets are used. ie there are probably bucket systems out there that auto-invoice another bucket when you go over; or perhaps others that have it in their terms of use that you get billed some form of overage charge anyway.

      It would be better if the provider lets you set limits (eg per min/hour/day/week/month); but I guess that depends on their business model.

      (Possible reply: “You should limit in your application!” -> better to have limits at both ends by both parties, layers of security. In practice the 1st party is going to screw up a lot :P )

      1. 1

        Yeah if you have an incentive to get the limiting right and they have an incentive to get the limiting wrong, just implement the limiting yourself. Even if they’re not knowingly, intentionally getting it wrong, incentives are incentives. They’re not going to maintain code well that is losing them money, no matter how morally upstanding they are. And you’re incentivised to be really careful.

    2. 2

      The majority of the companies I worked for prefer “entreprise pricing”, because it allows to know exactly how much will be paid, each month/year.

      Some of accounting services simply refuses to pay for a service they don’t know in advance how much will cost, or to “plug a credit cart on a subscription”.

      Also, pay-as-you go may end up in a huge bill when volume suddenly increases, due to a bug or some DDOS/scraping. Fixed quotas allow you to get notified before.