Firebase
Google's backend-as-a-service — NoSQL database (Firestore), auth, hosting, functions, and more. The most popular BaaS for mobile/web apps. Free tier, generous limits. Easy to start but vendor lock-in and NoSQL limitations.
Firebase Inc. (acquired by Google) · Founded in 2011, acquired by Google in 2014
- Mobile apps needing a quick backend.
- Prototypes and MVPs.
- When you want auth + DB + hosting in one.
- Google ecosystem projects.
- When you need SQL/JOINs.
- Vendor lock-in concerns.
- High-scale apps (cost).
- When you need full backend control.
Definition
Firebase is Google's BaaS: Firestore (NoSQL document DB), Realtime Database, Authentication, Cloud Functions, Hosting, Storage, Cloud Messaging (push), Analytics, and more. Client SDKs for web, iOS, Android. Server SDKs (Admin SDK) for backend.
Why it exists
Building backend infrastructure (auth, DB, hosting, push) is weeks of work. Firebase provides it all so you can ship an app fast without a backend team.
How it works
Create a Firebase project. Add the SDK to your app. Firestore: collections/documents, real-time listeners. Auth: email, OAuth, phone. Functions: serverless triggers. Hosting: static hosting + CDN. Rules (Firestore/Storage security rules) control access.
Scaling limits
NoSQL limitations (no JOINs, limited queries). Vendor lock-in (Google-specific). Cost at scale (Firestore reads/writes billed). Security rules complexity. Limited SQL/analytics.
Cost shape
Spark (free) tier is generous. Blaze (pay-as-you-go) for scale. Firestore reads/writes billed. Can get expensive at scale.
Alternatives
- Supabase — Postgres-based, open-source, less lock-in.
- AWS Amplify — AWS ecosystem, more complex.
- Custom backend — Full control, more work.
Failure modes
- NoSQL query limitations.
- Vendor lock-in.
- Security rules complexity.
- Cost at scale.
- Firestore pricing surprises.