4 ms·

Agreed. I've used Firebase for a couple internal company projects (right after they left beta) and I was able to quell any misgivings our AMs and PMs had about

by beebs93 12y ago

Agreed. I've used Firebase for a couple internal company projects (right after they left beta) and I was able to quell any misgivings our AMs and PMs had about relying on 3rd party startup services by explaining the sheer amount of time saved by not building their functionality ourselves. I've been holding back on using it for client work as the same people can't get past "only a year old service so not ready for production", but now with Google's backing and them making it clear it's not just an acquire-then-abandon startup I have more ammunition to sway pessimistic minds when a Firebase backend is warranted.

SiVal 12y ago
The sheer amount of time saved won't help you if it goes away, and it could go away in many ways: canceled, poorly maintained until it eventually becomes unreliable, price raised until you can't live with it but can no longer live without it, etc. It's quite a risk building your business on a single-source product from a vendor whose business wouldn't be significantly different whether that product succeeded or failed. I hope Google will resolve this by open sourcing Firebase, making it safe to commit to, while providing great paid hosting for it, making it a better choice to pay them for the "sheer amount of time saved", the maintenance, backup, etc., without having to bet the survival of your company on how committed Google ends up being to this minor product over the years to come.