Firebase Explained — Fast Start, and the Exit Costs Are the Product
Firebase is not a database. It's a bet: hand your entire backend to Google's opinions and ship a working app in a weekend — auth, data, sync, push, hosting, all of it. The bet pays brilliantly at the start, and the costs arrive later, shaped exactly like the shortcuts.
This episode takes the whole platform apart: the founding decision (delete the middle tier) that explains every feature and every trap, the two-database confusion, modeling without joins, the security-rules discipline that keeps you off the breach lists, and the pricing dynamics nobody reads until the invoice.
9 concepts:
1. The Suite — ~10 products wearing one name. Auth, Firestore, Realtime DB, Storage, Functions, FCM.
2. The Two Databases — Realtime DB vs Firestore: the classic trap. Default Firestore; keep RTDB for high-frequency ephemera.
3. Realtime & Offline — sync you didn't write, offline you can't build in a sprint. Billed per read.
4. Modeling Without Joins — model the screens, not the entities. Fan-out writes, 1MB docs, sharded counters.
5. Security Rules — rules ARE your backend. Default deny, validate shape, test like code.
6. Auth & Push — the à la carte winners: Firebase Auth as a plain IdP, FCM as THE Android channel.
7. Cloud Functions — the middle tier, readmitted on Google's terms. Rules gate writes; functions do trusted work.
8. Pricing & Lock-In — the N+1 read bill (your schema IS your bill) and the one-way door.
9. The Decision — weekend MVPs and realtime apps: yes. Finance and dashboards: no. Auth/push: always.
The line to remember: Firebase isn't expensive — it's priced in arrears. You pay at scale for the backend you didn't build at the start.
The opposite bet — Supabase, where the backend IS Postgres — has its own episode on the channel.
#Firebase #Firestore #BaaS #MobileDevelopment #GoogleCloud #Backend #SystemDesign #InterviewPrep #AppDevelopment
[prepforge:firebase]