3 ms·
> don't reinvent the wheel, and if you try, you'll probably get it wrong This should apply x100 for security related matters. I feel people only seem to bring
by seanwilson 7y ago
> don't reinvent the wheel, and if you try, you'll probably get it wrong
This should apply x100 for security related matters. I feel people only seem to bring this up with regards to hash functions and encryption but I think this should always encompass auth as well.
I use Firebase for auth. It saves development time, there's no user limit on the free tier even and it's battle tested.
- Kkoala 7y agoI think this is a common misconception that there are no limits for Firebase for auth. There are limits https://firebase.google.com/docs/auth/limits https://firebase.google.com/docs/auth/limits on free tier and on paid tiers too.
- seanwilson 7y agoWhich limits do you think are a problem? A lot of them seem to be about avoiding abuse e.g. New account creation, 100 accounts/IP address/hour
- Kkoala 7y agoFor example, if you want to do email verification the limit is 1000 emails/day. Though for paid tiers the limits seem reasonably high.
- seanwilson 7y agoThe Blaze plan is one of the paid tiers that has the higher limit. It's pay as you go so it's free if you have low usage.
- quickthrower2 7y agoDoes it have to be a physically seperate service, or is using a library good enough to count as not reinventing?