CST363 week 7
This week I learned about MongoDB, and I’ve got to say, it’s really interesting, especially since I’ve mostly worked with SQL databases like MySQL and Oracle in the past. The biggest difference I noticed is how flexible MongoDB is with data. In MySQL, you’ve got strict schemas, tables, and relationships that are great for keeping data structured, while MongoDB is more laid-back, letting you store documents without needing to define a strict schema upfront. That flexibility feels more dynamic, especially when dealing with unstructured or constantly changing data.
What I like most about MongoDB is how it seems perfect for modern apps where scalability and speed matter, like real-time systems or big data projects. But I can see myself sticking with MySQL for projects that need a lot of structure and consistency, like finance or anything that relies heavily on ACID transactions. Each has its place, but MongoDB is definitely cool for scenarios where you don’t want to be locked into strict data models.
What I like most about MongoDB is how it seems perfect for modern apps where scalability and speed matter, like real-time systems or big data projects. But I can see myself sticking with MySQL for projects that need a lot of structure and consistency, like finance or anything that relies heavily on ACID transactions. Each has its place, but MongoDB is definitely cool for scenarios where you don’t want to be locked into strict data models.
Comments
Post a Comment