Installing and Connecting to MongoDB
You can run MongoDB in several ways: installing the MongoDB Community Server natively on Windows, macOS, or Linux; running the official mongo Docker image for a disposable local instance; or using MongoDB Atlas, the fully managed cloud service, which avoids local installation entirely. Whichever route you pick, you end up with a running mongod process listening on a port (27017 by default) that clients connect to using a connection string.
Cricket analogy: Choosing between installing MongoDB locally versus using Atlas is like a local club choosing between building its own practice net versus renting time at a professional academy — both let you play, but one is self-managed and one is fully serviced.
Installing Locally or with Docker
On Linux, the MongoDB Community Server is typically installed via the official apt or yum repositories and managed as a systemd service; on macOS, Homebrew's mongodb-community formula is the common path; on Windows, an MSI installer sets it up as a Windows service. For a quick, disposable setup that avoids touching the host system at all, running docker run -d -p 27017:27017 mongo pulls the official image and exposes the default port, which is often the fastest way to get a local instance for development or testing.
Cricket analogy: Running MongoDB in Docker for a quick test is like setting up a temporary practice pitch for a single net session rather than maintaining a full home ground year-round, since you tear it down once you're done.
Connection Strings and MongoDB Atlas
Clients connect using a MongoDB URI connection string of the form mongodb://username:password@host:port/database, or for replica sets and Atlas, the mongodb+srv:// scheme, which uses DNS SRV records to discover all the hosts in a cluster without listing them individually. MongoDB Atlas, the managed cloud offering, provisions a cluster for you, handles patching, backups, and scaling, and gives you a ready-made mongodb+srv connection string plus an IP access list you must configure before any client can connect.
Cricket analogy: A mongodb+srv connection string that auto-discovers all cluster members is like a captain announcing just the team name at the toss, trusting the broadcaster's systems to already know every player in the squad, rather than reading out all eleven names manually.
Verifying the Connection
After starting mongod (or provisioning an Atlas cluster), you verify connectivity by connecting with mongosh and running a simple command like db.runCommand({ ping: 1 }) or db.adminCommand('ping'), which should return { ok: 1 } if the server is reachable and authenticated correctly. Common connection failures include the wrong port, a firewall or Atlas IP access list blocking the client's address, or incorrect credentials in the connection string, all of which show up as connection timeout or authentication errors in the client.
Cricket analogy: Running a ping command after connecting is like a broadcast engineer checking for a signal from the stadium camera before the match starts, confirming the feed is live before relying on it during play.
# Run MongoDB locally with Docker
docker run -d --name mongo-dev -p 27017:27017 mongo:7
# Connect with mongosh to a local instance
mongosh "mongodb://localhost:27017"
# Connect to a MongoDB Atlas cluster
mongosh "mongodb+srv://appuser:<password>@cluster0.abcde.mongodb.net/myapp"
# Verify the connection from within mongosh
db.runCommand({ ping: 1 })MongoDB Atlas offers a free-tier M0 cluster that's sufficient for learning and small projects, making it a common way for beginners to get started without installing anything locally.
Never commit a connection string containing a real username and password to source control. Use environment variables or a secrets manager, and remember that a MongoDB instance bound to 0.0.0.0 without authentication enabled is publicly exploitable if exposed to the internet.
- MongoDB can be installed natively, run via Docker, or used as a managed service through Atlas.
- The default MongoDB port is 27017.
- Connection strings use the mongodb:// or mongodb+srv:// scheme.
- mongodb+srv uses DNS SRV records to auto-discover cluster hosts, common with Atlas and replica sets.
- Atlas requires configuring an IP access list before clients can connect.
- Use db.runCommand({ ping: 1 }) in mongosh to verify connectivity.
- Never commit real credentials in a connection string to source control.
Practice what you learned
1. What is the default port MongoDB listens on?
2. What connection string scheme is commonly used to connect to a MongoDB Atlas cluster?
3. What must you configure in MongoDB Atlas before a client can connect?
4. Which command verifies a live connection to a MongoDB server from mongosh?
5. What is a fast way to get a disposable local MongoDB instance for development?
Was this page helpful?
You May Also Like
The Mongo Shell and mongosh
How to use mongosh, MongoDB's modern JavaScript-based shell, for interactive queries, scripting, and administration.
What Is MongoDB?
An introduction to MongoDB as a document-oriented NoSQL database, how it differs from relational databases, and when it makes sense to use it.
Documents and Collections
How MongoDB structures data into documents and collections, including field types, embedding versus referencing, and the _id field.