Conclusion / Conclusion

Press O for more options
3:13

Video Transcript (English)

Congratulations! You’ve completed the first step in your MongoDB journey and you're on your way to becoming an expert. But there’s much more to learn!

Let’s recap what you did in this unit.

First, you learned the difference between relational and non-relational databases, and the unique advantages offered by MongoDB.

Next, we took a tour of the MongoDB ecosystem, learning how MongoDB achieves high availability and scalability through its distributed system architecture.

From there, we briefly discussed what makes MongoDB special, the document model.

With that, we jumped into the architecture of MongoDB, which includes documents, collections, databases, nodes, and clusters.

We discovered that MongoDB was natively designed to operate in a distributed environment. This means all data is spread across many nodes and machines globally to ensure automatic failover and horizontal scalability.

This led us to learn about replication, read and write concerns, and sharding, MongoDB’s solutions for high availability, consistency, and scale.

We learned that replication is the process of storing multiple copies of data and synchronizing them across multiple nodes. If one node goes down, the data is still available as the other nodes take over.

MongoDB also allows you to manage the tradeoff between availability and consistency by setting read and write concerns appropriate for your application needs.

Similarly, we discovered how sharding ensures MongoDB can scale exponentially.

Rather than upgrading to a larger machine,sharding distributes the workload across multiple servers. Each shard contains a subset of data, forming a single logical database or 'sharded cluster.'

We shifted our focus to Atlas, MongoDB's database as service, and how it takes away much of the overhead of database management.

We discovered MongoDB Atlas's deployment options, such as shared and dedicated tiers.

During deployment, MongoDB allows you to select your cluster tier, cloud provider, and region. You can even select multiple providers and multiple regions to make your system even more resilient.

We also explored Atlas's robust security features that are automatically applied as well as advanced features available to add extra layers of protection. It satisfies authentication and authorization requirements and many security certifications.

Then, we created our first Atlas account and deployed a free-tier, shared Atlas cluster.

We also created our first database user and password, and connected to our cluster.

Then we loaded sample data into our cluster, and viewed documents using the UI.

Finally, we explored some features in the Atlas UI, including the command line tools, metrics tools, online archive, and the performance adviser.

Alright, we are just getting started and there is so much more to learn! Keep up the good work and see you next time.