MongoDB write concern for durability

Write operations in a mongoDB environment includes insert, update, delete. These operations modify the document. In versions prior to mongoDB 2.6 write concern had been of primary importance to ensure the durability of write operations. So, what exactly does a write concern mean? It reports details on the status of a write operation. This can be a success or a failure. MongoDB clients can choose to determine the level of write concern. Writeconcern as such provides durability of informaiton and comes with the cost of performance impact. MongoDB clients will have to wait if the write concern level is set to advanced. Starting mongoDB2.6 write concern is combined with write operation as part of latest write protocol enhancement. This makes the durability simple as this does not have to be set explicitly. In a typical mongod instance write concern can be configured with following options w - specifies required number of acknowledgements before returning j - requires writes to journal before returning wtimeout - time limit to prevent write operation from blocking indefinitely. If set to 0 this is disabled. Values of 1 and greater enables this In a typical sharding, mongos instance passes the write concern on to the shard How does MongoDB enterprise offers security features that helps enterprise firms secure data? Security in mongoDB extends to LDAP and kerberos authentication. For mongoDB instances running in Linux it is now possible to have active directory integration possible using centrify suite. Centrify 2014.1 suite offers single-sign on solution that helps users in an enterprise to make use of a single user account to access all the applications