使用Firebase烈火计划安全吗?

本文介绍了使用Firebase烈火计划安全吗?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我有一个非常简单的问题，从未找到答案.什么时候会使用火焰计划支付费用?在您拥有信用之前，您是否会购买一些信用和火力基础作品?信用达到0并重新填充时会发生什么.之后，firebase会立即开始工作吗?

I have very simple question, never found answer for that. When are paid costs for using blaze plan? Do you buy some credit and firebase works till you have this credit? What happens when credit reaches 0 and is refilled. Does firebase start to work after that immediately?

还是您每个月都根据使用的金额付款?如果您犯了编码错误或成为某些黑客的目标，这可能会带来非常不愉快的惊喜.可以为整个月的一些无限循环上传文件牺牲100美元的信用额，但可能不会牺牲100000美元...

Or do you pay after every month, based on what was used? This could bring very unpleasant surprises if you make coding mistake or become target of some hacker. One can sacrifice 100$ in credit but probably not 100000$ for some infinite loop uploading files for whole month...

推荐答案

Firebase Blaze计划是随用随付"计划.计划，如 Firebase定价页面所示.这是一项后计费服务，这意味着您将在月底按使用量付费.

The Firebase Blaze plan is a "pay as you go" plan, as indicated on the Firebase pricing page. It is a post-billing service, meaning that you get billed for your usage at the end of the month.

该月中，您可以在Firebase控制台中跟踪服务的使用情况(以及价格).

During the month, you can track your usage (and thus pricing) for the service in the Firebase Console.

如果您收到的帐单价格超出预期，则请联系Firebase计费团队，它将与您一起调查原因.

If you ever get a bill for an exponentially unexpected rate, reach out to Firebase's billing team who will work with you to investigate the cause.

如果您正在积极开发代码或可能进行更改而导致无限次读取或类似操作，则建议您使用仿真器套件，以防止产生意外费用.

If you're actively developing your code or are likely to make changes that result in infinite reads or similar operations, I'd recommend running and testing the code with the emulator suite to prevent racking up unexpected charges.

是的一个示例，禁用在达到特定条件时停止使用计费，但确实涉及其中，并带有以下警告:

There is an example of disabling billing to stop usage when a certain condition is hit, but it's pretty involved and comes with this warning:

此示例从您的项目中删除了Cloud Billing，并关闭了所有资源.资源可能无法正常关闭，并且可能会被不可挽回地删除.

This example removes Cloud Billing from your project, shutting down all resources. Resources might not shut down gracefully, and might be irretrievably deleted.