Firebase is an engineering decision, not a religion
Where managed services create leverage, where they create pressure, and how to keep architecture honest.
flowchart TD
A[Project constraints] --> B{Managed primitives help?}
B -->|Yes| C[Use Firebase deliberately]
B -->|No| D[Own the backend boundary]
C --> E[Keep escape paths visible]
D --> EWorking note
Firebase is useful when authentication, real-time data and managed operations create more leverage than custom infrastructure. It is weaker when the domain needs strong relational consistency, complex reporting or independent service boundaries.
Why it matters
A technology choice should reduce project risk. If it becomes an identity, the architecture stops listening to the product.