Cloud Firestore Data Modeling (Google I/O'19)
HTML-код
- Опубликовано: 3 июл 2024
- So, you're building your first app using Cloud Firestore, and these NoSQL databases are still new to you. How can you set up your data in Cloud Firestore so that you can a) Perform all the queries you want, while b) Keep everything running quickly, and c) Not spend too much money? Let's find out together by looking at some common use-cases and app types, and see how to implement these on Cloud Firestore.
Watch more #io19 here:
Firebase at Google I/O 2019 Playlist → goo.gle/2GSFVqN
Google I/O 2019 All Sessions Playlist → goo.gle/io19allsessions
Learn more on the I/O Website → google.com/io
Subscribe to the Firebase Channel → goo.gle/Firebase
Get started at → firebase.google.com/
Speaker(s): Todd Kerpelman
T1165A event: Google I/O 2019; re_ty: Publish; product: Cloud - Databases - Firestore; fullname: Todd Kerpelman; 
Наука
This guy is the best teacher. Solid presentation
hell yeah dude ! This guy can also probably explain definite integration to 11yr olds
Agree!
True ❤️❤️❤️
He's so funny and explains really well
@@tilakmadichettitheappdeveloper no
This talk is so good. He begins with the exact "emotional" state where probably many are in, not wanting to mess things up for the future but not yet having the most extensive experience in the scale-up side of things. Discussing approaches and questions like denormalization or storing data in larger documents vs. sub-collections from this point of view is super helpful and something mostly not found in documentation
Thank you so much for your kind message of support 🙂
Data modeling rules (according to the presentation):
1. Documents have limits (size, field indexes, operations at the same time…)
2. You can only fetch documents (not specific fields for each document)
3. Billing is mostly based on the number of documents you touch
4. Queries search for indexed fields across a collection
Data modeling rules (according to the presentation):
1. 16:05 Documents have limits (size, field indexes, operations at the same time…)
2. 18:29 You can only fetch documents (not specific fields for each document)
3. 20:44 Billing is mostly based on the number of documents you touch
4. 24:11 Queries search for indexed fields across a collection
This was the best IO talk I saw - you're an excellent presenter Todd!
The API analogy it's so clever, blow my mind and make me understand the NoSql idea immediately
Thanks, this is the 1st video everyone coming in to firebase should watch. Really a big thank you
Todd is great! I can listen to him present for a whole day. The audience doesn't look enthused though, even with GoT references!
Todd is an extremely good speaker! All of his Firebase Firestore videos are amazing. Thx!
This guy knows what he's doing ! Keep going 🤘🤘
very crisp talk and he touched most important use cases we may face when we implements firestore.
Videos like this tells me that, the best things in the world are free of cost.
A very helpful introduction for us long in the tooth SQL based types! Thank you.
I've been looking at so many tutorials and videos, and this is easily the best one. He directly answers several questions I might have as soon as news things are brought up, and I finally feel like I have a solid understanding of how I should go about this
Thank you for the crystal clear presentation!
I'm really surprised how comfy is listening Todd and learning new stuff. This is exactly how good teacher should look! 😃
This is a presentation that must be seen by every developer who want to use Firebase Cloud Firestore. It should be recommended by all tutorials and courses out there!
I like that you explained the tradeoffs very clearly. It's a realtime db after all, and some basic features we expect don't work the way we think it they should. However, there should be guides that show us how to work around these basic features we can't have (reference, ORs, etc.)
This is my best lecture of the firestore
As a developer with a SQL background now developing my first app with Firestore and NoSQL this was the exact talk I needed to watch. It's all clicking now.
For explaining complex concepts Todd is the G.O.A.T.
"If didn't like this, my name is (not Todd) and I was talking about android.." 🤣🤣🤣🤣
That made me laugh loudly.
Great presentation and I picked a lot, it's like developing an app from scratch to end in 40.5 minutes.
Greetings from Tanzania 🇹🇿
It's great to watch someone who is this good at his job!
Todd is so fun to watch! He joked about it in the talk but he really *does* make a talk about database structures sound exciting.
Considering using firebase despite everyone advising against it, because of this guy Todd :)
Great talk, tells a lot about the possible scenarios and how we may handle with them.
Awesome talk! One of my all time favorite presenters!
Todd was excellent. Helped me nerd out on Firestore :D
Nice job Ted! Thank you for being such an awesome presenter/teacher 👍
This was really good. The topic that was talked about last, was exactly the problem I was facing. Thank you for the solution!
this is very helpful, thanks Todd!
Very good insights in such short time. Lot of things to unlearn for somebody coming from long experience in RDBMS world.
This really helped. Thank Todd.
Amazing presentation! I feel like I really understand how Firebase data modeling works and the pros and cons of NoSQL databases after watching this video.
Great to hear!
Building a product is one thing but providing support and taking it to the next level is a whole new story. Firestore lacks basic features like support for IN/OR queries, automated backups etc. But people like Todd make things very simple and that is such a life saver as information is organized and comes from a trusted source. Thanks Todd for making this possible :)
Fantastic. Brilliant presentation. Covered everything one may want to know.
Glad you enjoyed it!
Thank you! This is awesome explanation!
Collection Group Queries! Finally🙏
Extremely helpful, thank you!
Zombies in the Resident Evil games are more alive than this crowd, however I can tell you guys that I laughed, learned and I'm psyched up while watching this. Awesome job!
Great talk and very helpful. Thank you
Loved it just what i needed to get started
Very nice session. Very comprehensive
Wonderful presentation . Hats Off .
Fantastic explanation, thank you very much for share your knowledge
Such a great presentation
Amazing presentation. I love how consumable this information is. This crowd isn't very lively!
Very good!! Thanks for the lesson Todd =D
This guy made a really funny Game of Thrones joke, and everyone in the audience had a bloody straight face
Collection group querying! Wooooo~~
Wooooo~
such a nice presentation. got to learn a lot of things !!
Exceptional content Todd, thanks a lot !
Glad you enjoyed it!
Best teacher ever!
its good to know that i am using firebase in correct manner 😎
Very Great Explanation
Awesome explanation!
Amazing explanation!
Amazing.. thanks
From 2021 :D
All my questions has fixed
This guy really explains very well, cracks joke from time to time and the crowd just doesn't get it. :D :D :D
No, actually they get it. Its just the mic is centred to him
Great presentation and nice feature reveal 😀
Great! Thanks for sharing, Todd. :clap :clap
Awesome lecture!
Great presentation, Reto Meier! ⭐⭐⭐⭐⭐ for Android Studio
Glad you like it!
Great explanation!
Great job Todd
I do care about my fish's birthday.
@@ToddKerpelmanCorp how dare you, sir
But nobody does
I beleive it would be a hatchday
lol
It's been a year. I think he forgot his fish's birthday
Excellent talk
Who would've thought Robin Williams would be the best tech presenter and teacher ever?
Great presentation
Thank you!
Love this guy
Love it! great talk
great video!
This s**t is 10 out of 10. Great work.
That George RR Martin joke didn't get the love it deserved
awesome stuff
finally collection group queries 🔥🔥🔥
We know we are nerds when we use 🔥🔥🔥 with collection group queries
You guys should really make a video on how to structure data for a social media app :P
Totally agree! Working on one now.
Firestore is not suitable for social media app, I guess.
Nikolai Fedorov, waiting to see it
Greetings from Tanzania 🇹🇿
yeah
Amazing!
Thank you for the support, Gerardo!
Let's start :)
great video
amazing video
🔥
Awesome !!!!!!!!
Great!.
I understood the references
Thanks
Hey firebase It's firestore not firestone . See the thumbnail.
Anyway i love you firebase 💗
Best video to introduce firestore to us. Anyone has summary documents which recaps this content?
We're excited to hear you've enjoyed the video! You can head over to firebase.blog/posts/2022/05/whats-new-at-google-io for a summary of what's new at I/O! You can also continue to grow your skills by visiting our learning lab over at
✨ io.google/2022/learning/ ✨😄
undestood for the first time
Thanks for that, create video
nice!
A backend would help filtering privat fields so the client only gets the fields that are *public" for a given document. Also, a backend could leverage Redis caching to minimize cost. So backend + Firestore is the best of both worlds imho
If you didn't like it I talked about Android Studio :D
I didn't expect this to be that great!
For the case of finding restaurants with a certain dish like "Chicken Tikka Masala", he proposed that due to this new feature of "collection-group query" we can now solve this problem if the menu-items are placed in the restaurant docs as sub-collections instead of a map.
However it does not make sense to me, because the collection-group query for example: collection_group("menu_items").where("name", "==", "Chicken Tikka Masala") will only return the documents of "menu_items" but not the actual "restaurants" which have that menu item. However in case where I have a map of menu items inside of restaurant doc, I can actually query on the restaurant sub-collection to get actual restaurant docs containing that menu item.
Can anyone clear me point, If I am missing something?
@@ToddKerpelmanCorp
So if I want to query the restaurants documents which contain a certain dish in their menu-items subcolllection, not the dishes documents at all, I have to copy restuarant data (which are more than just the name in my case) all over my items in the subcolllection? Isn't that an overload ?
Shouldn't that be improved so I can somehow get the parent documents only ?
Also presenting the problem of, when any field in the parent is updated, I have to also repeat that update in all of it's subcolllection items (which is the most annoying problem I'm trying to avoid in NoSQL database scheme for many-to-many relationship)
@@ToddKerpelmanCorp also, why can't I perform collection group query by document ID instead of fields ? That's something that should exist
ONE CHICKEN TIKKA MASAAAAAAALA FOR THIS GUY RIGHT NOW!
Is there a timeframe for native location queries a la GeoFire?
I lov it!
❤🔥
Also it is worth to mention, that if Author changes name, all printed books remain his old name :)
great