Mongodb - Difference between running “mongo” and “mongod” databases

Question

So, I'm sure I'm missing something simple here, but when I run mongo as a daemon (using mongod --fork or just mongod), I see different database content than if I just run "mongo" on the host machine.

My only assumption is that the data is being stored somewhere other than /data/db when it's running just the shell, and switches to /data/db when I boot the mongod. In that case, how do I get at my data when running mongod?

Answer 1

• mongod is the "Mongo Daemon" it's basically the host process for the database. When you start.
• mongod you're basically saying "start the MongoDB process and run it in the background". 
• mongod has several default parameters, such as storing data in /data/db and running on port 27017.
• mongo is the command-line shell that connects to a specific instance of mongod. When you run mongo with no parameters it defaults to connecting to the localhost on port 27017. If you run mongo against an invalid machine: port combination then it will fail to connect (and tell you as much).

Answer 2

Mongod(Short for Mongo Daemon) is a framework process used by MongoDB server to get things done. This method is responsible for managing the whole MongoDB server tasks such as accepting requests, responding to users, managing memory requirements of MongoDB server operations and other things essential for MongoDB Server to run.

Whereas Mongo is a JavaScript shell interface to MongoDB, that shows a powerful interface for system administrators as well as a way for developers to examine queries and operations directly with the database which also provides a fully functional JavaScript environment for use with a MongoDB