5 ms·
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 Fireb
by 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 agoIt 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 agoI 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 agoNo 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.