You guys are discussing MongoDB from 2009. The database has evolved since then.
- There is a new replication protocol for replica sets, improving the election process.
- WiredTiger has been introduced and became the default storage engine.
- Journaling guarantees durability.
- Sharding architecture has changed. Config Servers are now deployed as Replica Sets and some of the tasks that used to be managed by mongos now are managed by the config servers.
- Storage efficiency has been added through compression.
- Security has been improved with encryption at rest.
- The aggregation framework has more options for BI.
- There are a variety of different indexes that can be created to improve query performance.
- and finally, stop saying MongoDB is schemaless because it is not. There is a schema in place and this schema is flexible enough to be polyform.
These are features available today in 3.4.
You might have issues in the past, but if you really understand the newest architecture, you are capable of seeing how much MongoDB has grown since 2.4.
- There is a new replication protocol for replica sets, improving the election process.
- WiredTiger has been introduced and became the default storage engine.
- Journaling guarantees durability.
- Sharding architecture has changed. Config Servers are now deployed as Replica Sets and some of the tasks that used to be managed by mongos now are managed by the config servers.
- Storage efficiency has been added through compression.
- Security has been improved with encryption at rest.
- The aggregation framework has more options for BI.
- There are a variety of different indexes that can be created to improve query performance.
- and finally, stop saying MongoDB is schemaless because it is not. There is a schema in place and this schema is flexible enough to be polyform.
These are features available today in 3.4. You might have issues in the past, but if you really understand the newest architecture, you are capable of seeing how much MongoDB has grown since 2.4.