Quota vs no-quota features

[mnakalay]

Hello,

I am uncertain if I understand quotas, or more exactly how different their consumption is from non-quota features.

My understanding is, I first create a feature. Upon subscription, I add charges to that feature. That's how many of the feature the subscriber can consume.

Then as they consume it, I use the consume() method to keep track. When the limit is reached, the method will throw an error.

Your explanation of quotas is

These features have an unique, unexpirable consumption, so they can reflect a constant value (as used system storage in this example)

That got me confused:

• So quotas have no limits?
• can quotas be cyclical?
• We don't need to add charges for them on subscription
• Your setConsumedQuota() throws an error if the charge is higher than the limit the same way consume() does, so how is it unexpirable?

In your example with file uploads, does it mean they can upload as many files as they want, or are they limited?

I am confused about the whole idea of the "unexpirable consumption". Can you help me understand please?

Many thanks.

[lucasdotvin]

Hey!

You got good questions here! In fact, the documentation about the quota features is a bit confusing. 😅 You can think of them as features that do not gain new monthly usage (they are statical). For instance: if you have a 100 GB quota feature and consume 10 GB, it will not recover in the next month. Instead, you'll be with 90 GB until you add or remove files because the consumption does not expire. If you use a regular feature, it'll renew periodically and your users will be able to upload 100 GB every month (consuming 200 GB in 2 months, 300 GB in 3 months, and so on).

I hope I made it clear, let me know if I can help with something more! 🚀

[mnakalay]

OK. Now I understand :)

Thank you!