Reasons to (Not) Use Firebase
summary
Covers concrete tradeoffs of using Firebase: it speeds initial launches and reduces early backend costs compared to hiring a backend team, but lacks region control, has limited query/filtering and causes auth lock-in that complicates GDPR and financial use. Describes a migration path from Firebase to AWS, including challenges restoring a 350 GB nightly backup and the need to write adapters to extract and reshape deeply nested JSON, and recommends options like local SQLite/Rx or a JWT identity server to avoid vendor lock-in.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:56Infrastructure evolution in Brazil
- 7:28Firebase and its ecosystem
- 14:13Firebase: data migration issues
- 18:32Firebase: data schema issues
- 20:21Firebase: authentication issues
- 23:13Firebase: data search issues
- 25:43Vendor lock-in and exit difficulty
- 28:53Alternative auth solutions
- 31:50Recommendations and cost comparison
- 33:40Conclusion and Q&A
related talks
46mFirebase Realtime Database Deep Dive
04m6 tips to follow in a post-GDPR world
26mChoosing the Right Cloud Database For Your Indie iOS App
37mBuilding Scalable Apps with Cloud Firestore
23mWhat's an App Without Data?
34mTo SQL or NoSQL? Firebase is the Answer
26mHow to go serverless in a post-GDPR world
01h 15mFirebase Is More Than Just PUSH Messages