3 ms·

Oddly, they have no problem shutting things off when the limits of their free plan are exceeded: https://firebase.google.com/docs/projects/billing/firebase-pri

• pclmulqdq 2y ago
  That cutoff is rarely truly a hard cutoff. The limits are often too low to have a natural test of that, though.
  • ryao 2y ago
    They could always make the amount over that is given due to their cutoff enforcement being less than perfect free, as it likely already is on the free plan. That would avoid the risk of unbounded bills associated with going on a paid plan.
    • pclmulqdq 2y ago
      Most of the cloud providers have a less-than-perfect cutoff. It's worse than the cutoff of the free plan, though, because the free plan can be slowed down to have better enforcement, while the commercial plans have performance SLAs to hit.
• chen_dev 2y ago
  Limits Reached -> PubSub Notification -> Shutdown Sequence. Because it's a free plan, the delay between 'limits reached' and actual shutdown only incurs the cost of providing the service during that brief period, not the potential liability of overcharging that might exist on a paid plan.
  • ffsm8 2y ago
    Is that really a problem though? Just don't bill beyond the cap then and leave the last few requests free, too. Or write a disclaimer that the billing cap doesn't necessarily cut off at exactly that amount and that there might be an overcharge. I am pretty sure most people would be okay with either of these options, we didn't need a perfect system, just one that works well enough