Cloud Firestore Data Modeling (Google I/O'19)

[@the1yearexperiment]

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

[@Firebase]

Thank you so much for your kind message of support 🙂

[@KristianDamian]

The API analogy it's so clever, blow my mind and make me understand the NoSql idea immediately

[@f4xxf4xx]

This guy is the best teacher. Solid presentation

[@tilakmadichettitheappdeveloper]

hell yeah dude ! This guy can also probably explain definite integration to 11yr olds

[@anonymosranger4759]

Agree!

[@SusanthCom]

True ❤️❤️❤️

[@DodaGarcia]

He's so funny and explains really well

[@marthasolis2281]

@@tilakmadichettitheappdeveloper no

[@gbhall]

This was the best IO talk I saw - you're an excellent presenter Todd!

[@guillempuche]

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

[@valdineiferreira4814]

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

[@dugtrioramen]

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

[@DodaGarcia]

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.

[@excitingfruit]

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.

[@adarsh_hatwar]

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 :)

[@soumitripattnaik]

Videos like this tells me that, the best things in the world are free of cost.

[@broken_arrow1813]

Todd is great! I can listen to him present for a whole day. The audience doesn't look enthused though, even with GoT references!

[@marcelvarela9058]

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!

[@Squad2ND]

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!

[@deville295]

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.)

[@vaishankur]

Considering using firebase despite everyone advising against it, because of this guy Todd :)

[@bunnihilator]

Thanks, this is the 1st video everyone coming in to firebase should watch. Really a big thank you

[@grzegorzgumieniak6460]

I'm really surprised how comfy is listening Todd and learning new stuff. This is exactly how good teacher should look! 😃

[@raymondmichael4987]

"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 🇹🇿

[@SamGerrans]

It's great to watch someone who is this good at his job!

[@postfixnotation9829]

Todd is an extremely good speaker! All of his Firebase Firestore videos are amazing. Thx!

[@2yaya123]

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.

[@Firebase]

Great to hear!

[@mohamedhussainsh7913]

very crisp talk and he touched most important use cases we may face when we implements firestore.

[@donathmm3881]

This guy knows what he's doing ! Keep going 🤘🤘

[@JSANL]

Collection Group Queries! Finally🙏

[@glynvilesatago3441]

This guy really explains very well, cracks joke from time to time and the crowd just doesn't get it. :D :D :D

[@iamsurajgiri]

No, actually they get it. Its just the mic is centred to him

[@404-HANDLE_NOT_FOUND]

A very helpful introduction for us long in the tooth SQL based types! Thank you.

[@kaibe5241]

Todd was excellent. Helped me nerd out on Firestore :D

[@anandakumarsanthinathan4740]

Fantastic. Brilliant presentation. Covered everything one may want to know.

[@Firebase]

Glad you enjoyed it!

[@locusm]

For explaining complex concepts Todd is the G.O.A.T.

[@AtomicCodeX]

This guy made a really funny Game of Thrones joke, and everyone in the audience had a bloody straight face

[@DeependraSolanky]

Very good insights in such short time. Lot of things to unlearn for somebody coming from long experience in RDBMS world.

[@tommytower47]

This was really good. The topic that was talked about last, was exactly the problem I was facing. Thank you for the solution!

[@ImpactAICANADA]

Amazing presentation. I love how consumable this information is. This crowd isn't very lively!

[@goat5249]

Great presentation, Reto Meier! ⭐⭐⭐⭐⭐ for Android Studio

[@Firebase]

Glad you like it!

[@kevinjacyna7323]

Thank you for the crystal clear presentation!

[@Meknassih]

Exceptional content Todd, thanks a lot !

[@Firebase]

Glad you enjoyed it!

[@verryondrums]

Awesome talk! One of my all time favorite presenters!

[@dobleuxyz]

Amazing!

[@Firebase]

Thank you for the support, Gerardo!

[@beside5915]

This is my best lecture of the firestore

[@moomoomamoo]

Collection group querying! Wooooo~~

[@spicepirate]

Wooooo~

[@82invisinle82]

Great talk, tells a lot about the possible scenarios and how we may handle with them.

[@Prime-o8f]

That George RR Martin joke didn't get the love it deserved

[@401-Unauthorized-u5b]

Thank you! This is awesome explanation!

[@VINNUSAURUS]

You guys should really make a video on how to structure data for a social media app :P

[@nfokl]

Totally agree! Working on one now.

[@jeet5401]

Firestore is not suitable for social media app, I guess.

[@raymondmichael4987]

Nikolai Fedorov, waiting to see it Greetings from Tanzania 🇹🇿

[@lazymacs2823]

yeah

[@LucasMDias]

I do care about my fish's birthday.

[@hunterheston]

@@ToddKerpelmanCorp how dare you, sir

[@asafmazon7]

But nobody does

[@IAmSamuelCharpentier]

I beleive it would be a hatchday

[@leeboyin945]

lol

[@jkojkojkojk]

It's been a year. I think he forgot his fish's birthday

[@TheChaitanyaDubey]

Great presentation

[@Firebase]

Thank you!

[@VitorLucasOFICIAL]

Very good!! Thanks for the lesson Todd =D

[@TheodoreRavindranath]

Awesome crash course on Firebase

[@antopolskiy]

Great talk and very helpful. Thank you

[@AkshaySood1]

Nice job Ted! Thank you for being such an awesome presenter/teacher 👍

[@estebanmtz4315]

Such a great presentation

[@balajipadmanabhan4590]

Wonderful presentation . Hats Off .

[@かやひこ]

finally collection group queries 🔥🔥🔥

[@saminsharar3933]

We know we are nerds when we use 🔥🔥🔥 with collection group queries

[@marinesuper6441]

Best video to introduce firestore to us. Anyone has summary documents which recaps this content?

[@Firebase]

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/ ✨😄

[@sunjin222]

Loved it just what i needed to get started

[@manupandher39]

its good to know that i am using firebase in correct manner 😎

[@lukecole5056]

Who would've thought Robin Williams would be the best tech presenter and teacher ever?

[@fabrizziocht]

Fantastic explanation, thank you very much for share your knowledge

[@ValAllenSamonte]

this is very helpful, thanks Todd!

[@darshans1190]

such a nice presentation. got to learn a lot of things !!

[@paracha3]

Very nice session. Very comprehensive

[@RamdanCode]

Amazing.. thanks From 2021 :D

[@MaximilianBeck]

Great presentation and nice feature reveal 😀

[@arthurcebrian]

Best teacher ever!

[@andrewerdle]

This really helped. Thank Todd.

[@praveenaanand6389]

Hey firebase It's firestore not firestone . See the thumbnail. Anyway i love you firebase 💗

[@lvenir4702]

This s**t is 10 out of 10. Great work.

[@vijayhi3ic]

ONE CHICKEN TIKKA MASAAAAAAALA FOR THIS GUY RIGHT NOW!

[@himbary]

Excellent talk

[@preetgandhi1233]

Very Great Explanation

[@GintsPolis]

Also it is worth to mention, that if Author changes name, all printed books remain his old name :)

[@LarsRyeJeppesen]

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

[@ivammagalhaes7155]

Great! Thanks for sharing, Todd. :clap :clap

[@troybailey175]

Extremely helpful, thank you!

[@codewithtae6637]

Is the 1 mb size rule for documents the reason you need to use cloud storage for images and the sort?

[@tareqalbeesh9149]

great video!

[@arvidurs]

Is there a timeframe for native location queries a la GeoFire?

[@thejohnfranco]

All my questions has fixed

[@bakerkawesa]

Awesome lecture!

[@GeireenG]

If you didn't like it I talked about Android Studio :D I didn't expect this to be that great!

[@diegocuevac]

Great explanation!

[@makemypetgamedevprocess6475]

Love this guy

[@WendelSchultz]

It was nice to see that what I sort of intuited was confirmed by the Googs here. I'm still a bit unsure how to model organization/team permissions around documents and collections, as well as organization invitations. Using his example, my restaurant has 3 people with sufficient permissions with respect to the restaurant to update the restaurant document. I suspect some sort of restaurant "admin" array with user IDs or something (possibly in an admin collection for permissions reasons), where the write permission evaluates request.user.uid is in the admins array or something. So then doing admin invitations becomes work of could functions, upon login, matching login email/phone principal against invited emails/phones to snag uid. I think. I'm trying to find my legs here.

[@LarsRyeJeppesen]

I think using a backend doing your requests would help in your case.

[@abdifatahnour8839]

Excuse me i wanna ask you a question. Can firebase services daily usage be upgraded Just like free plan 20k reads to 1m reads per day

[@stofstik]

This presentation was you know, sort of, kind of, like, nice, right ; ) JK, thanks for the presentation!

[@icoffeenz]

amazing video

[@susmitvengurlekar]

Why not use reference for orders? Each part of order points to relevant docs other collection for example restaurant info

[@LarsRyeJeppesen]

Imho you want the order data to be a snapshot of how data looked at order time. No referencing.

[@susmitvengurlekar]

@@LarsRyeJeppesen ohk! Realised just now . The details such as quantity, price, and other things can change. Thanks

[@LarsRyeJeppesen]

@@susmitvengurlekar You're welcome ;)

[@UjjwalKumar-wg4wu]

awesome stuff

[@francoisguezengar6255]

You might think about changing the typo "firestoNe" in the cover of the video. It would be a cool name for a next service on firesbase though ;).

[@eduardorabanal2803]

great video

[@asafmazon7]

Love it! great talk

[@glauberdesouzasilva930]

I would like to know how many reads that are executed inside a document that contains other collections. It's possible?

[@belqisshida5345]

Is Cloud Firestore a good selection for a bank account? Can it be safe and reliable to save people's money which is a number to the Cloud Firestore? My concern is reliability and security. Any suggestions?

[@FarryEntertainment]

How do you make a chat system with Firebase then?

[@mohammedmaaz1765]

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?

[@n0krashy]

@@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)

[@n0krashy]

@@ToddKerpelmanCorp also, why can't I perform collection group query by document ID instead of fields ? That's something that should exist

[@mannie-live]

If there are more restaurants with the same name and one of them changes its name how will this work? As far as I understand there is no way to select by combining fields like Name = xxx and address = XXX.

[@lukecross5439]

Why was so are null the class? I think that have a many of people, but, have less.

[@kaibe5241]

NoSQL stores should use write-time relationships like graph databases, so that you can in fact, do join-like queries in one call, super fast.

[@acche-rc]

Skip to 26:34 for the new collection group queries

[@princesimfukwe9158]

When are you guys inviting