4 ms·

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 storag

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 !

snyp 6y ago
It is so far behind! It can't even handle social login reliably.
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 ago
  I 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 ago
  Google 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.
cwhiz 6y ago
I really like Firebase but for me it is way too risky for anything but personal projects. Vendor lock on the entire stack. 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.
- offtop5 6y ago
  It depends, if your company has the money to hire a dedicated backend programmer then Firebase wouldn't be needed. 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
- gman83 6y ago
  I don't really understand why people say this. I'm using Firebase in my Flutter app but I've completely abstracted out the implementation into service classes. The business logic just calls my service auth, fetch data, etc... doesn't know anything about firebase. I could swap Firebase out for another provider no problem, no lock in.
  - cwhiz 6y ago
    No problem? Come on. The entire Firebase stack is closed source, and only available through Google. It's not like you can take your Firebase back-end and move it to Digital Ocean. If you want to go elsewhere you have to export everything, and put it somewhere else, with some other technology stack. Your idea of vendor lock is radically different than mine.

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 !

snyp 6y ago

It is so far behind! It can't even handle social login reliably.

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 ago
I 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 ago
Google 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.

cwhiz 6y ago

I really like Firebase but for me it is way too risky for anything but personal projects. Vendor lock on the entire stack. 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.

offtop5 6y ago
It depends, if your company has the money to hire a dedicated backend programmer then Firebase wouldn't be needed. 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
gman83 6y ago
I don't really understand why people say this. I'm using Firebase in my Flutter app but I've completely abstracted out the implementation into service classes. The business logic just calls my service auth, fetch data, etc... doesn't know anything about firebase. I could swap Firebase out for another provider no problem, no lock in.
- cwhiz 6y ago
  No problem? Come on. The entire Firebase stack is closed source, and only available through Google. It's not like you can take your Firebase back-end and move it to Digital Ocean. If you want to go elsewhere you have to export everything, and put it somewhere else, with some other technology stack. Your idea of vendor lock is radically different than mine.