3 ms·
Would love to hear others experiences. I’ve used both firebase and amplify. My concerns with firebase are: Google kills products at a whim, security rules are
by randomsearch 6y ago
Would love to hear others experiences. I’ve used both firebase and amplify.
My concerns with firebase are: Google kills products at a whim, security rules are horrible.
Amplify seems more powerful so more likely to work long term, directly uses AWS “full strength”.
Concerns with Amplify: their npm libraries seem to be a colossal mess (they have old and new libraries that have to be partially used in tandem, and the docs use a sprinkling of each), plenty of odd bugs seems to crop up, the DataStore cache confuses me, idiomatic usage is not obvious - the fact that it’s composed of so many layers means it is not obvious which level of abstraction to interact with, and CLIs have flaws that seem blindingly obvious in design, which makes me worry about quality overall.
Should I stick with Amplify of return back to warm and fuzzy firebase (before Google dump it at random) and risk its limitations?
- offtop5 6y agoI would say either use Firebase or roll your own ( a open source self-hosted framework would fit this). Firebase seems to be one of Google's stable projects, so I love it. I've used it for at least 4 years. I'm only using it as a hobbyist, so take all my experiences with a grain of salt.
- reilly3000 6y agoGoogle hired the firebase team, integrated their product into the platform and completely rebuilt the DB with Firestore, and made Firebase into their mBaaS powerhouse that supports hundreds of thousands of apps. Its not some free product that's drawing a lot of resources, it's their entire mobile app developer strategy, and under many contracts to maintain the service.