Firebase team mentioned that it is a database for small applications like chat apps, but i wanted it to perform like mongo, mongo can easily handle data with millions or billions of documents in just few microseconds , i wanted even firebase to perform similar way
Nice introduction, I wouldn't say deep dive but it is a good start! What is really interesting me is the offline part, and the fact that "Transactions are not persisted across app restarts" as said on the iOS / Android documentation. So I am wondering if there is any video indicating how to handle possible loss of write transactions when user is offline? A video "Mastering offline with Firebase database" would be awesome.
So there seems to be a lot of focus on scaling across devices, but how does this handle scaling complexity? For example, MongoDB offers a concept of Collections, which while not analogous with tables in SQL solution space does offer a very nice mechanism for much more complex data management. This either seems to be missing or glossed over - further to that what of data types? While "String" or Stringlike seems to be sufficient in any chat or grocery list, geospatial data would be great to allow a user to tap into Maps etc. As it stands right now I really want to like Firebase but it feels like more like an alternate to Meteor rather than an alternate to a real back-end.
This was a deep dive for beginners. Covering the basics of structure, realtime, saving data, and offline. There's only so much you can cover from the start when you're live on stage. If you're looking to go deeper, then you should totally keep an eye out for future episodes of Firecasts. What topics are you interested in learning?
I am sorry to be an ass, but "a deep dive for beginners" is a contradiction in terms. To stay with the SCUBA reference, it's like saying "we're doing a deep dive to ten feet". I am looking forward to more deep dives though.
Maybe deep dive was the wrong wording, my original title was "Go 0 to 60 with the Realtime Database". The point of the talk was to take explain the basics of the Realtime Database in greater detail.
This is the Firebase video I've wanted since I first heard about it.
As a beginner with RTDBs I wanted to say thank you. This is a great introduction to these elements and I feel that I have a better understanding.
One of the best talk on firebase realtime database.
Thanks for sharing such valuable information in a short period of time 👍👏👏👏👏
Not exactly about Realtime Drive, it's more how to work with one of real time databases called "Firebase" :)
i want to know how much scalable is firebase realtime database..???
It's Google scale now, right +David East?
it would be great if it scales like other nosql databases like mongo..
vishal gaware What do you mean? (Don't know how mongo works) Firebase couldn't scale as you wanted it?
Firebase team mentioned that it is a database for small applications like chat apps, but i wanted it to perform like mongo, mongo can easily handle data with millions or billions of documents in just few microseconds , i wanted even firebase to perform similar way
How about firebase database for petabytes of data..??
Nice introduction, I wouldn't say deep dive but it is a good start!
What is really interesting me is the offline part, and the fact that "Transactions are not persisted across app restarts" as said on the iOS / Android documentation. So I am wondering if there is any video indicating how to handle possible loss of write transactions when user is offline? A video "Mastering offline with Firebase database" would be awesome.
Great video mate, im subbed, keep it up :D
So there seems to be a lot of focus on scaling across devices, but how does this handle scaling complexity? For example, MongoDB offers a concept of Collections, which while not analogous with tables in SQL solution space does offer a very nice mechanism for much more complex data management. This either seems to be missing or glossed over - further to that what of data types? While "String" or Stringlike seems to be sufficient in any chat or grocery list, geospatial data would be great to allow a user to tap into Maps etc. As it stands right now I really want to like Firebase but it feels like more like an alternate to Meteor rather than an alternate to a real back-end.
This was a deep dive in the same way that surfing is a deep dive.
This was a deep dive for beginners. Covering the basics of structure, realtime, saving data, and offline. There's only so much you can cover from the start when you're live on stage. If you're looking to go deeper, then you should totally keep an eye out for future episodes of Firecasts. What topics are you interested in learning?
I am sorry to be an ass, but "a deep dive for beginners" is a contradiction in terms. To stay with the SCUBA reference, it's like saying "we're doing a deep dive to ten feet".
I am looking forward to more deep dives though.
Maybe deep dive was the wrong wording, my original title was "Go 0 to 60 with the Realtime Database". The point of the talk was to take explain the basics of the Realtime Database in greater detail.
0 to 60 would have been a great talk name!
:)))))))
Great tutrial love it ❤❤
Excellent
real time db functionality works if i used Rest api to access db?
Isnt it what couchdb can do for years?
I just like the way speaks
How to code remove or delete in firebbase?
Are you missing a "" at the end of groceyItems reference?
Greeeeat Video! I learned a lot.
And what about persistence in JS?
David speaks for real time trafic in fast forward talk mode 😂
#askfirebase hello how to sort the newest data on top using a recyclerviewer
I love fire base. is development is so much easier Han android
Nice
Awesome TV works without cable ...Ant TV with digital black box.......
Try stuff done on this video directly into your android phone
play.google.com/store/apps/details?id=com.shivang.managefirebasedatabase
Firebase is seriously boring and confusing especially when working with collection or loading data to a feed no proper way to add a Like or star
such a waste of time, He could've sum this in 3 4 min video.