So far in this course I have come to understand how relational databases work and why they are so much more powerful than basic spreadsheets. One of the big concepts has been normalization which is all about organizing data in a way that reduces repetition and keeps everything efficient. I’ve learned how to break large tables into smaller ones and link them using foreign keys to maintain relationships between different types of data. SQL has been the major focus, specifically using JOIN operations to pull together data from multiple tables at once. Indexing is another key thing I’ve picked up. It’s crucial for speeding up queries, especially with large amounts of data. We’ve also worked with SQL views, which are virtual tables that make complex queries simpler. And figuring out how to auto-generate primary keys which has made it clearer how databases manage unique identifiers for records.

Looking ahead, there are still a few things I’m curious about:

How can I use indexing in really large databases without slowing down write operations?

What’s the best approach for managing data when relationships aren clear-cut, like in NoSQL databases?

How do transactions work to keep data consistent when lots of people are accessing a database at once?

Comments

Post a Comment

Popular posts from this blog

This week I focused a lot on understanding time complexity and recursive analysis. It was challenging at first to figure out how to break down recursive functions and write the correct recurrence relations. Applying the Master Theorem was especially tough because I had to carefully identify each part of the formula and decide which case applied. I also spent time reviewing the difference between Big O, Big Omega, and Big Theta, which helped me better understand how to describe the efficiency of an algorithm. These concepts took time to click but working through examples really helped.
Read more
Over the past few days I completed the final sections of the Google Cloud Digital Leader certification. These modules reinforced my understanding of how cloud systems scale, maintain availability, and how services like compute and storage work together in real-world environments. At the same time I worked on drafting my capstone presentation. I organized it around the three certifications and focused on clearly explaining what I learned and how the concepts connect. Overall, this stage was about bringing everything together and making sure I could clearly communicate what I’ve learned.
Read more
When I started this course I thought Software Engineering would mostly be about writing code and learning new tools. After week one I see it’s more about understanding how different parts of a system connect and work together. Building and testing the REST API showed me that software isn’t just about making something run, it’s about planning, structure, and testing to make sure it’s reliable and easy to maintain in the long run.
Read more