3 ms·
I feel like Firebase has a great hackathon demo, but still find it hard to believe that people might actually be using this for their actual backend. The lock-i
by TheAceOfHearts 12y ago
I feel like Firebase has a great hackathon demo, but still find it hard to believe that people might actually be using this for their actual backend. The lock-in is extremely high, and migrating to something else would be extremely challenging.
- padho 12y agoI think it really depends on what kind of data is stored. For something like a chat it is a really nice solution in my opionion. If you have to apply complex queries and need full control over your data I would recommend a "real" backend. For instance, we use Firebase for our community feed on http://spotpot.co http://spotpot.co but I would not use it to store user accounts there. In the end it is always a trade off but consider that for heavy real time applications a service like firebase can not only be convenient but also save you load on your infrastructure.
- DannyBee 12y agoCertainly you realize that most startups don't care about that? They expect they'll spend the time to rearchitect it later on (rightly or wrongly)
- nbardy 12y agoAs someone who is currently building out some products with Firebase I don't think the cost to swap platform would be too high as long as you isolating your data layer properly. I'm writing it with om/clojurescript; however, the same would be true for reactjs or any declarative setup. The only code I would need to rewrite would be the read and write hookups to the server.
- lygaret 12y agoAnd, you know, the real-time data backend itself.
- whatts 12y ago100% agreed. Consider this to prevent the lock-in: https://news.ycombinator.com/item?id=8563103 https://news.ycombinator.com/item?id=8563103