way too risky to use it for startups. Google may discontinue this project at any time and you have to spend months to rewrite everything for another database. IF google open source it and we will be able to install it on premise and patch without Google, that would be ok. So, I would recommend to use PostgreSQL instead.
Way to risky not to use for startups, IMO. What would you prefer, spending half your time doing backend development to get a system that might be 80% as reliable as Firebase on the off chance that your startup will survive long enough for your custom engineered solution to bare fruit, or spending all your time actually building your product and launching quickly so you can determine whether or not your startup is even viable?
They always say that. Google's internal customers also get to continue access after a product has "been retired" (eg. Chrome Web Store still using Google Wallet's web payments) and are in a different position than Google's external customers when it comes to negotiability and notification period.
Well, yes, but if they decide to discontinue the service, or increase the price, this is no guarantee that all other users will get the same treatment as Alphabet companies.
Same argument for enterprises can be had here. Way too risky to let the existing house of cards (stack) to perch atop a product that can be discontinued at anytime (I'm looking at you, Microsoft!). Google needs more revenues since ad money is shrinking so they would make sure that you get vendor-locked. Once shit happens, you are provided with a more expensive alternative, or consultancy services provided by certified vendors (again, looking at you, Microsoft!).
