MongoDB Atlas — 3 of X. Setup your MongoDB Atlas — Build Your New Cluster.

Now, let’s focus on setting up your MongoDB Atlas to ensure you’re paying zero dollars! Right? By the end of this blog, you will have set up your first MongoDB Atlas cluster. If you’ve missed our previous writing about – MongoDB being not being that complex – you can read about it here on medium or here on Dev3lop.

Also, if you need help signing up to MongoDB Atlas, then be sure to follow along in our previous tutorial.

Robots building your MongoDB, you just guide the robots. Click, click, click. Beep Boop.

Alright, once you’ve signed up to MongoDB Atlas, you’re going to dig into the process of generating your database. But being a revolutionary tech space, they don’t call it ‘building your database.’ Rather they call it ‘Build Your New Cluster!’ I can dig it.

Build Your New Cluster on MongoDB Atlas (it’s free I promise.)

Check it out, it’s free, so when you get to this page, it selects a paid plan, just ignore that!!!

After the signup: You’re going to notice it bumps you into a screen that shows you’re paying for something… The first thought in my head was..,

What the heck. I thought this was free.

We thought MongoDB was free..

We thought this database would be free and it is free but the user experience will push you into a paid plan.

So, don’t get jaded by this wonky user experience, it’s free, it’s free. We explain below that you need to, scroll down and change it to free. Look at the screenshot below, it will clear that up for you. Yes, it’s free, a tiny scroll down you will see Instance Size, click on the Free version!!! Okay, I’m glad I could help with that tiny workaround. It’s my specialty.

Okay, now that you’re back in the free mode, can we get started?…

You should see 0.00/4eva!

Setting up Clusters in MongoDB Atlas.

Cluster Name — Name your cluster wisely, you cannot change this later.

You can only name your Cluster once… Probably something technical to it. I’m not scared yet.

Naming your cluster, don’t hurt yourself. Keep it simple. Numbers help people keep track of large quantities of clusters. Also, if you hit ESCAPE by accident like I did, you can click back, and I’m not entirely sure what that does just yet. Will let you know… I’m going to name it… TestyMcTesterSon.

Do I win an award? Nope. Okay, moving on.

MongoDB Version — All clusters launch with the WiredTiger™ storage engine. FYI: MongoDB 3.4 with WiredTiger™ — All M0 instances launch with this version.

Well, here we go into the technical world. This absolutely is going to drive you to ask, ‘what is WiredTiger, and what is a storage engine. This is where most users might drop, just because they have no idea what this has to do with their reporting environment. NO fear, let’s skip it. (Actually, I read about it already, so I can skip it. haha)
Uh oh, maybe skipping around isn’t working out. Time to read about what WiredTiger is all about.

Regrettably, this is where MongoDB team has let this content funnel get really technical really fast.

Consider we try to write for the average business users – feel free to skip and keep moving.

— — — — — — — — — Just skip this part if it doesn’t click, continue below.

WiredTiger Storage Engine

Starting in MongoDB 3.0, the WiredTiger storage engine is available in the 64-bit builds.

Changed in version 3.2: The WiredTiger storage engine is the default storage engine starting in MongoDB 3.2. For existing deployments, if you do not specify the --storageEngine or the settingstorage.engine, MongoDB 3.2 can automatically determine the storage engine used to create the data files in the --dbpath or storage.dbPath. See Default Storage Engine Change.

Document Level Concurrency

WiredTiger uses document-level concurrency control for write operations. As a result, multiple clients can modify different documents of a collection at the same time.

For most read and write operations, WiredTiger uses optimistic concurrency control. WiredTiger uses only intent locks at the global, database and collection levels. When the storage engine detects conflicts between two operations, one will incur a write conflict causing MongoDB to transparently retry that operation.

Some global operations, typically short-lived operations involving multiple databases, still require a global “instance-wide” lock. Some other operations, such as dropping a collection, still require an exclusive database lock.

— — — — — — — — — Did you skip that?
— — — — — — — — — Cool, keep it as is.
— — — — — — — — — Wing it with me.

Okay back to earth, wrapping up our clusters in MongoDB Atlas.

Back to earth, let’s get this done and worry about errors later 🙂

Can we just get through this form quickly?

Sorry, we just assumed you wanted to read this quickly!

Keep it set to 3.4.

And know, the product is currently in version 3.6.

Thanks, but we don’t have anything set up. Give us one sec.

Cloud Provider — Choose the cloud provider for this cluster… Only one option from what I’m reading. Keep it as is.

Amazon Web Services is your only option to run the MongoDB Atlas free version.

FYI, don’t change this, or you will have to pay. So, wing it. Go go go!

Just do it, click it, confirm… & deploy… Your clusterMCclusterSons.


Just kidding… Get this done. I trust you.

Also, you’re not going to be able to use an email address. It doesn’t explain that here, and it will explain it when you do it wrong!

Then tell the internets you’re not a robot, click that checkbox. Okay, now you have that done.

MongoDB Atlas — Finding the simple in the complex. 1 of X.

MongoDB Atlas — Signup to MongoDB Atlas. 2 of X

MongoDB Atlas —Connect an IP, Make it Public, Delete Access — 4 of X.

MongoDB Atlas —Install MongoDB Compass— 5 of X.

MongoDB Atlas — Setting up MongoDB Compass Community — 6 of x.


Next steps: For the love of Peter — don’t skip this step or you’re going to be SOL when it comes to syncing anyone up with your super-so-cool-data.