FWIW it's worked well for us, but our application has the follow characteristics:
1) Our data is relatively small and well-scoped, so we're only querying small amounts of data (maybe 10-20 queries each of <50 records) from any individual client
2) We care a lot about real-time, so we want data manipulation on one client to show up pretty immediately on the other
3) While we'd definitely save money switching to a Postgres instance, we're not spending that much to begin with on Firebase.
I think these play well to Firebase's strength. In a previous life I built an app that sucks in a lot of data exhaust and then visualizes it... IMO Firebase wouldn't have worked well for that.
I think these play well to Firebase's strength. In a previous life I built an app that sucks in a lot of data exhaust and then visualizes it... IMO Firebase wouldn't have worked well for that.