Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does the limiter affect firebase reads/writes? #23

Open
purpleh00d opened this issue Jan 12, 2021 · 2 comments
Open

Does the limiter affect firebase reads/writes? #23

purpleh00d opened this issue Jan 12, 2021 · 2 comments

Comments

@purpleh00d
Copy link

purpleh00d commented Jan 12, 2021

The problem with firebase as you might know is that there's really no way to stop users from abusing your db by spamming functions calls. Even if you do stop them, the fact that they still call them might result in a huge bill anyway, which is what really scares me and can put any business out.

So basically, my question is: do I have to be careful about billing anyway, even if I use this limiter?

Also... if I choose Firestore to save that data limit, then there will be a limit of 1 Mb per document, will it be handled by this library or by ourself ?

Thanks

@oguzeray
Copy link

its $0.06/100K read after 50K free daily for Firestore. $0.40/1M invocations after 2M free monthly.
So if you do you math right, spammers will pay more electriciry bill than your google bill. Let them.

@Jblew
Copy link
Owner

Jblew commented Jun 13, 2022

There are two backends: Realtime Database and Firestore. If you are concerned with costs use the Firestore one. It is optimized for low write count :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants