Closed laurentpayot closed 6 years ago
We'll see if I need to create another package, I hope I don't :) This is something I'll look into
I don't see any references to it being deprecated. Where is it stated that the realtime database is going away?
No, it's not deprecated. Firestore is in beta
They are 2 separate products, firebase real-time database is not going away.
use Cloud Firestore for your new projects.
and
Expect to see new query types, more robust security rules, and improvements to performance among the advanced features planned for Cloud Firestore.
They don't say anything about future improvements of the Realtime Database. It's dead. For me there is a high probability for the Realtime Database to be shut down within a couple of years. I hope not, but I think so.
They said in the hacker news story (https://news.ycombinator.com/item?id=15393396) that they are separate products for separate use cases and that they will support both.
Thanks for the link @ssijak This comment by the Firebase founder is reassuring: https://news.ycombinator.com/item?id=15395343
Regarding deprecation: you can be comfortable continuing to build on the Realtime Database. We don't intend to deprecate either database, since both are useful in different situations, depending on what you're building. We recommend using the Realtime Database for a number of usecases[1] We're not posting a "Realtime Database will be supported for X years" statement because many may interpret this as "the Realtime Database is deprecating in X years", which isn't the case.
Along with improved querying, the offline capabilities for javascript SDK for firestore seems at first sight the most significant change to implement (although the interest of offline for a web app doesn't strike as key at first sight, the instantaneous response of the cache is good for fluid UI updates).
Firebase real-time database already works nicely when disconnected
From a few of the interviews circulating the web, it does seem like Firestore will become the "preferred" database for new users. There's no mention of Real-Time DB deprecation, but the emphasis is clearly shifting to Firestore going forward.
@neovive That's pretty clear just from the link in the first post. Here's the relevant bit.
If you're comfortable with a product in beta, use Cloud Firestore for your new projects. Cloud Firestore offers additional functionality, performance, and scalability on an infrastructure designed to support more powerful features in future releases.
That tone seems to indicate that once cloud firestore is out of beta, they'll be recommending it for all new projects.
can't wait for a firestore support
Hey everyone!
I've started using Firestore recently and I can't wait for vuefire to have support on this amazing product. I've seen not so many changes have to be done. Maybe it's useful to have separated fields on a component to support both:
...
firebase: {
myCollection: db.ref('/my-collection'),
},
firestore: {
myCollection: db.ref('/my-firestore-collection'),
},
...
Is there anybody willing to implement it?
Actually the Firebase ecosystem is (will be) using Firestore as its prefered database, the other "legacy" database being the Real Time Database (RTDB).
So as Firebase is no more mainly a database but rather a collection of tools (whatever database, auth, hosting, etc.), maybe we should use the following notation:
...
rtdb: {
myCollection: db.ref('/my-rtdb-collection'),
},
firestore: {
myCollection: db.ref('/my-firestore-collection'),
},
...
And while waiting for Vuefire to support Firestore the native solution is less convenient but quite easy:
https://firebase.google.com/docs/firestore/query-data/listen
Simply detach listeners at the beforeDestroy
hook.
Yes, it's as simple as before, didn't took me long to get something working but I found a bug that I reported, so I'm holding back a bit for the moment. I'm not a fan of having both things at the same time. If Firestore is meant to be the successor of Firebase realtime database, I prefer having different versions. In the worst case you can always both packages.
@posva +1 for different versions.
+2 for different versions.
IMHO it isn't upward compatibility completely. RTDB's latency is less than Firestore's. They also strongly said, "We'll support both."
But all in all, we can think it is a successor.
@Yatima-Kagurazaka It's nice you found a temporary solution but please don't promote it here. Right now I cannot code much for personal reasons, but I'll publish an official version as soon as I can
I'm sorry. I put it here for reference to develop vuefire better than expected. I won't do like this.
What's the update for firestore on vuefire? ;)
I'll get an alpha release in the coming weeks with the basics features and probably a stable version with the full set before 2018
Sorry for not getting it done sooner but I was just super busy with personal matters and I'm still not at full capacity 😄
Closing in favour of #145
Breaking (pun intended) news: https://firebase.google.com/docs/firestore/rtdb-vs-firestore
Looks like a vuefire fork is needed…