Has AWS caught up to firebase yet , we went with Firebase as a backend for our Flutter web project and it's been a dream.
Web hosting , auth, Nosql data storage !
Web hosting , auth, Nosql data storage !
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?
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.
Amplify tried to compete with Firebase by glueing together a bunch of disparate AWS services. It has less overall vendor lock, but you are still functionally tied to an AWS service. Again, for me, too risky.
If you're comfortable with the vendor lock, Amplify is just not even close to Firebase. Amplify feels like some hacky side project in comparison to Firebase.
But if you're trying to solo develop or working on an extremely small team Firebase can do a ton of the heavy lifting. I can put a server up ,but I find backend programming to be very boring
Your idea of vendor lock is radically different than mine.