Firestore and NoSQL Research

I wanted to model my data schema properly, so it was time for some research.

Published on August 16, 2020

Since my last blog post, I've logged roughly 5.5 hours of development (research) time for my personal project. I was mainly researching NoSQL and Firestore stuff. My research efforts took me down the path of mainly NoSQL data modeling.

Progress

This table is missing something, but I'm not sure what.

Dev Week Dev Hours
Aug 11-15 5.5

I spent the week doing some research on how to properly model my data using Firestore. Firestore is a NoSQL database, so my research led me to data modeling techniques used with NoSQL. What I didn't really appreciate before was that data needs to be stored differently when compared to SQL, because the database engines are completely different. I thought there was just some small difference, like denormalizing what I would have in a SQL design, but there's more to it. For example, you can nest data in a NoSQL database, but it's encouraged to keep data shallow as a rule of thumb. The common theme I see is that your application has to do more work to keep your data consistent. The whole topic deserves a separate post that I may or may not write. Either way it definitely piqued my interest. I have one more blog post to read and then I'm going to get back to actually putting what I learned into practice.

Life

Life this week was grand. I finally made a dinner that my daughter likes. It's called Hungry Man, a simple recipe of ground beef, veggies, pasta sauce, and macaroni. It usually takes some coaxing to get her to eat what I make, but not this meal. Aside from the food win, I was able to get out to the park with my family for two days in a row. We even had ice cream after one of the park visits. It was a really nice family weekend that made me smile and filled my heart with love. This is why I don't dedicate more hours to my projects, because those family moments make life rich.