Model Relational Data in Firestore NoSQL
ฝัง
- เผยแพร่เมื่อ 8 ก.ย. 2024
- Learn how to model and structure data relationships with the Firestore NoSQL Database. We build simple one-to-many and many-to-many relationships by modeling a twitter-inspired app. angularfirebas...
- Firestore Structuring: firebase.googl...
- NoSQL Document DB - en.wikipedia.o...
![Megan Thee Stallion - Neva Play (feat. RM) [Official Video]](http://i.ytimg.com/vi/TpYTyAaTRts/mqdefault.jpg)
Oops, meant to say "no greater than 1MB" at 1:10 - I hope this gives you some ideas for basic relational modeling in Firestore, but there are more advanced techniques that I will cover in the future.
I’d love to see more techniques about data modelling. Keep up the good work :)
😂 "documents need to be at least 1MB or smaller" left me scratching my head
Anyway, thanks for the content.
your technique of demonstrating possibilities is simply awesome, straight to the point, without diversions. well-rehearsed.. awesome ! :)
how to check the size of the document ?
@@peet91pop I m not got the general content of this video, can I conclude it become 1 sentence "To create relationship in NoSQL, we can use both Normalize and Denormalize method?" Normalize is separate them to Collections, And Denormalize is use "Object Field"
This is perhaps the only channel where I watch in 1x and pause often.
That's funny because this video is the first video I watched in 1.75x
I was thinking the exact same thing lol
I usually watch on X1.5 , or even faster in case I'm familiar with the subject
But here on fireship no no no 😂 X1 speed and I need100% of my brain
Exactly . So dense with valuable information
@@gamesland2067 hey
For anyone watching this in Feb 2019 and following along, there is no more "object" field for the documents. It's now called "map".
you saint
Arigatou senpai
The hero we need, not the hero we deserve.
nice to know. Just started working with it :D
cheers!
I am a Spanish speaker and I appreciate your speech clarity and the knowledge of this channel. Thank you so much.
6 years old and it still helped me plan out the structure for my project. Thank you!
OMG, seeing this for the first time in my life to try to do something using flutterflow and firestore. Glad to finally see some noSQL stuff (I'm VERY SQL oriented for over 20 years using relational databases).
Actually taught me NoSQL and Firestore at the same time. Amazing videos as usual.
Still useful today. Wow your videos have come far, and so has your voice!
I agree, one of better videos that explains how to apply relational techniques to Firebase. This is what SQL developers are looking for to come over to Firebase.
Exactly, that have prevented me from entering into firebase in the past till recently I gave it a try and this video summarizes all what I have read along the way and what I have implemented.
Hands-down best video series on Angular and Firebase! Keep up the Firestore videos! We'll definitely need it since it's still in beta.
Jeff, you make learning more fun for me. Thanks
5:20 It is now possible to make queries across collections and subcollections with the same name using collection group queries.
The best explaination on Data modeling in Firestore👏👏
That's a great introduction to the NoSQL mindset thanks you
of all modeling videos, this one is the best. Thank you so so much!
I just started working with databases and found firebase and your videos make understanding it so much easier and quicker. Great work!
Exactly the information I needed.
The user -> tweets model is applicable to so many other applications.. like stores -> products.
Which is how this helped me resolve my data structure.
Thanks!
I just watch your half of your videos because of the voice combined with the background jingle :P no joke, love them
Hands down the best TH-cam channel for coding
3:34, you can now actually do this! Firebase is really growing and allows you to defined those queries.
great Video .. Thanks from Germany Leonardo
Great explanation mate. Just what I needed.
Exactly what i needed, thank you. Realized that I should just go with a SQL db
this guy is on speed
Exactly, I was commenting on this. He is too fast. Although tutorial is good.
The speed is great!
@@StephenRayner ok
@@ajaykotiyal427 just slow it down in the TH-cam player!
Its called adhd
Great video Jeff, thank you! This was an excellent topic to cover. It confirmed what I already learned from talking to you in Slack, and gave me some extra insight.
Your content is super awesome! Maybe you could one day do a video on how to get data from firestore to datastudio, I bet it would be incredibly useful not only for me. Keep it like that.
It would be helpful to see examples of typical queries. How would we get the tweets a specific user has liked? All of the tweets liked by that user? The tweets of user A that were liked by user B? I think I understand the concepts here but it hasn't quite clicked in my mind. Probably I just need to try some of these exercises myself.
NoSQL feels so primitive compared to relational dbs. I quite like its simplicity but do feel uneasy by the lack of relations
Damn... this channel is A+ class.
Awesome videos man, simple and straight to the point! Keep it up
Always a very good content by the way. Thanks for sharing. I am a very satisfied Pro Member and highly recommend it to all.
+ Daniel I'm very glad to hear that, thanks for sharing your feedback :)
Wow I just implemented this approach using exactly the same method for a similar situation. I had problem with Firebase9 since I couldnt nest the likes inside a document inside a post So I decided to do take the easier approach and I was hoping the I didnt ruin my project.
But after I watched your suggested video I feel 100x more confident about it. Thanks alot ❤️❤️
finally i understand now how the noSQL work. thank for your awesome video.
Not an Angular guy but i use Firestore often this is truly amazing thanks alot
Thank you! What do you use Firestore with?
Angular Firebase Android development in native Java, actually modeling my current database using some of the principles you've mentioned
Nice and helpful tutorial and hard to find one like this addressing data modeling specifically for firebase! But I have to watch at 0.5 speed to fully understand the content lol!
Bro you deserve a subscribe!
I am so surprised that this is the same way that i was thinkink to use firestore database😁
At 6:12 it is stated that we can return tweets by multiple users and then at 6:20 it is stated that we can also scope a query to a specific user. My question is... is it possible to scope the query to multiple users (a friend list), lets say an array or user ID's?
I am also curious
awesome as always
Jeff, you are awesome!!!
+Mateja Thank you :)
thanks, answered really well the question, how we solve complex situations in noSql .... by yourself !
thank u it helps me a lot
No one can beat you sir
Is you??😳
5 yrs back ur voice 🤐🔥❤️
TH-cam recommends me this video while I am working on a Firestore implementation in Android. I wonder if they can view my PC.
Yes, yes they can
@Wafi Hartono Yes, it's me
I remember we use this technique with Firebase Realtime Database before Firestore and i can't see any news except modification on query code, any way thank you a lot for your tutorials.
The query methods are a big improvement + it gives you the flexibility for shallow queries when nesting. Thanks for the feedback :)
whaou!!! wath a nice topic on a nice video, thanks
Wow loved it
easy to understand. good job!!
awesome video bro, thank you very much
G’day, a noob query: @7:00 - There was a mention to check if an user has hearted a post by checking whether the document exists for userid_tweetid. Doing this operation at scale, wouldn’t it easily consume lot of GET requests?Would it be a better alternative to write the hearted tweet id per user basis to Firestore and sync the same in realtime back to the client so that the client always have the list of tweets thus making the check locally than to reach the server?
Amazing!!
Eu estava com duvidas quanto a construção dos relacionamentos, foi de grande ajuda esse video.
(I was in doubt as to the construction of the relationships, this video was very helpful.)
- Follower of Brazil
Hey Jeff, great video. Why don't you use the 'reference' data type? for a user document rather than creating a new field?
Thanks for the video. It would been better to first represent the relations as relational database and then showing how to do this in nosql way.I was watching you type but many times you were explaining some other concept like many-to-many. Difficult to follow thru.
I thought you'd demonstrate the use of 'reference' field type... any thoughts on that?
Keep up the great work! :)
My thoughts exactly.
Nice explanation
episode 63? is this part of some series? if so where can I find the full series or playlist?
Check his channel. He offers a bunch of free videos on youtube. He also has some paid ones on his site at fireship.io I believe. There's also a stripe community you can join. His videos are by far the most useful I've found.
Thank you so much bro I was lost
Awesome video +++++++++++++ 😃
Great explaination
But wouldn't it be extremely expensive to manage your data this way? If Firebase charges for every read and you want to get all tweets every time, and you have thousands of users and potentially millions of tweets
At that point you should be able to afford it.
That's true. That's why I often try to end up by not having smallest possible documents with relational data, but with redundancy for data, that is often read, but not often written (e.g. a tweet in this case). I thought costs might be also a topic of this video. Sadly it's not mentioned.
@@michaelraring9473 Danke bro!!
If you’re still looking for an answer to this, look up Google I/O 19 firebase data modeling on TH-cam. It counts as a single read so stay cheap
Hi Jeff, wondering if it is better using userId as the "Document ID" for "tweets" and any other collection related to the user. This way you can use:
/user/{userId} to show user information
/tweets/{userId} to list every users' tweets
/following/{userId} to list every followed user
/followed/{userId} to list every user following the user
I don't think so. This *may* be more appropriate to be applied on a server endpoint than on firebase. I have little to no experience here but it feels better to use the /model/{modelId} most if not all the times so you can always retrieve unique documents.
Basically, donot use nested collections. Instead, use collections as tables and documents as rows 😉👍
Yeah that was also my key take away. Also it seems if you pull in a document, the sub collection will not be included anyway so you might still need to make an extra call, which could might as well have been to a real collection.
you are awesome
how would you get all tweets along with up to date user data such as user name and age not just user id ... like joins in sql
Very good job explaining this. but one thing for sure it doesn't need to be in 9 mins
So, if I am creating a quiz app, and I in the end want to query what the average score of ALL users are, I basically have to have my questions as a root document, and add users ID's to each questions answer as an array? I.e. Question 1 > Option A > User 1, User 2, User 3. Then Question 1 > Option B > User 4, User 10, User 101. Then Question 2 > Option C > User 1, User 3, User 101.
Or am I missing the point here?
Really struggling with how to design a database where I can store users answers to the questions, but not only that, storing which question each user bookmarked for later review, and also make it possible for users to see statistics per chapter, counts of bookmarks per chapter/total questions, correct answers per chapter/total questions etc.
at 7:10 .. Does that mean we will need to make a document id for each user with a specific tweet? that a huge data
Did collection group queries made the part about the tweets obsolete?
Early in the video OP showed creating a document with userId and instructorId properties and claimed this was many-to-many. That's not mtm it's just two foreign key references from the same document to two documents in presumably the same collection. Maybe what OP meant to do was make the userId property and array of userId? Does firebase support multiple indexable values for a single field like elasticsearch?
great video
So how would you get a list of tweets a user hearted?
Query through the 'hearts' document where userID == desiredUser
Hi, this was a nice intro video for me. Do you plan to make longer video tutorials on this Firebase topic?
new to firebase..... dose it increase read and write count...or increase billing
does this create lot of document read and the cost will be pricey
Doesn't it look like what you're doing to solve any problem that arise from nesting collection (namely the impossibility to query all documents subcollection at once) removing the nesting by bringing the subcollection to the root to then use it exactly like any other relational SQL database ?
it just seems like SQL with extra steps and hurdles.
I am working on a project where videos will be displayed and users will be able to comment on videos. How will be the relational database for it on firestore.
7:16 will using a composite id of the User and Tweet lead to issues involving hotspotting? "Avoid high read or write rates to lexicographically close documents" - Firestore best practices doc. I'm currently in the process of implementing some backend logic that uses this idea, but I'm concerned that this idea won't work in the long run.
6:52 How do you get the user info from 'tweets' collection if there's no join? example output will be: USER ONE - 'User tweet this one.' , USER TWO - 'This is other tweet from this user'
Great tutorial! Can you please post a tutorial for 2 cascade dropdown list with array object thank you very much
@Fireship why not putting hearts collections under each user ? With and object {tweetId1 : true, tweetId558: true}. I would kindly like to know if this can cause issue or not ? Because liked tweets are linked to the users, so creating a collections under users/${userId} make sense no ? Instead of having it outside create the need to link it. And has you said even if the collections is big it's not a problem (if the user like tons of tweets should not be an issue). Cloud functions triggered where like or unlike will work the same for total count.
I always watch videos on this channel in 0.5-0.75x speed. He's going too fast for someone who's learning like me.
Hey, one question tho.
I understand why we normalized the structure so that we can query all the tweets in a single day if we want to. But what about if the user wants to see all of his tweets? Are we looking at some data duplication in this case?
Does the size of my db change the response time? Or has Google abstracted it enough to not make a difference?
Please open the subtitles for each video.Thanks
Hi Jeff, for the trick mentioned in 7:20 - Does a firestore call to check if the user has liked a post need to be made for every tweet he views? Will this not exponentially increase the read costs?
Great video! Keep it up! :)
+Alvin Will do, thank you!
Guys, check out JaguarDB, which is awesome. Time series data, geolocation data all
in one natively. Automatic time window rollup.
What is the background music it's so cool
How cloud function pricing works
Thank you keep it up! Any hints on when geofiltering will be available? :)
I don't know, but I hope to see geo query support soon. You can expect a video as soon as it becomes available.
I'm building an app with Angular and Firebase but would like to learn as much about Firebase (noSql) data modeling first. Any resources you can point me to. Thanks!
Do you know of any technique to reduce the number of document reads when querying a collection of posts? currently working on an app and it seems wasteful that just strolling through a paginated profile of a user can cause upwards of 100 reads when you have many posts.
Doesn't it require us to write data on multiple documents for updating a single field? Write is much more expensive than read.
is better to use collectiongroup
Does it work the same way in Datastore in google cloud?
Hi, I'm new to coding. Are these videos good for people trying to build a firebase database in Swift?
Do you have vue totural on firebase
Thanks ... Most cases is shopping cart ... Can you make structure and queries for that in the future ... Thanks again
Yes, I have a shopping cart structure planned for a pro video in a few days on angularfirebase.com