Percona Server for MongoDB Feature Comparison

Percona Server for MongoDB is based on MongoDB 3.0, and it is the successor to Percona TokuMX, which is based on MongoDB 2.4. The tables in this section will help you evaluate the differences.

Storage Engines

One of the biggest features introduced by MongoDB 3.0 and available in Percona Server for MongoDB is the pluggable storage engine API. This enables you to select from a variety of storage engines depending on your needs. Previous MongoDB versions (before 3.0) and Percona TokuMX can run with only one default storage engine.

The following table shows which storage engines are available.

  PSMDB MongoDB 3.0 TokuMX [1] MongoDB 2.4
WiredTiger YES YES NO NO
MongoRocks [2] YES NO NO NO
[1]TokuMX uses a proprietary storage engine similar to PerconaFT
[2]MongoRocks engine is currently considered experimental

Feature Comparison

The table below provides a comparison of important features to help you evaluate the differences.


It is assumed that you run Percona Server for MongoDB with the PerconaFT storage engine, and it is compared against MongoDB community edition running with MMAPv1. There are footnotes for cases when a feature depends on the storage engine or it is available only in the commercial enterprise edition of MongoDB.

  PSMDB MongoDB 3.0 TokuMX MongoDB 2.4
Hot Backup YES [3] NO YES NO
Audit Logging YES NO [4] YES NO
External SASL Authentication YES NO [4] NO NO
Geospatial Indexes YES YES YES NO
Text Search YES YES NO NO
ACID and MVCC compliant NO NO YES NO
Clustering Key Support NO NO YES NO
Sharding with Clustering Keys NO NO YES NO
Point-in-time Recovery NO NO [4] YES NO [4]
[3]You can use TokuBackup when running under PerconaFT or use hot backup functionality available in the MongoRocks storage engine
[4](1, 2, 3, 4) Available in MongoDB Enterprise Edition