Percona Server for MongoDB Reviews

Summary: Overall my experience with Percona has been great and i would recommend people to use it whoever uses MongoDB at a daily purpose. Great work by the team

Positive: I liked their logging feature and the flexible data structure which is very easy to use for people who are new to this!

Negative: There is no such major cons that i think but i would say that the documentation should have more practical examples like videos on how to use it.

Summary: Positive experience all around, simple to install and run, we hardly ever get alerts of issues on our Percona for MongoDB environment.

Positive: We've been running Percona Server for MongoDB for at least 3 years in an AWS environment, its been completely reliable, never had a Percona related issue. Performance has been steady and it enabled us to achieve several auditing requirements without purchasing the Enterprise Edition directly from MongoDB.

Negative: Minor quibbles - we had to write our own utilities to manage log recycling, would've been nice to have that included.

Summary: Overall, it's a good product with the very less debugging option, like sometimes it's very hard to know the error and sometimes showing unexpected behavior too.

Positive: - It's an open-source tool.
- Almost negligible downtime in my case.
- Increased flexibility with native format.

Negative: - Very limited troubleshooting options.
- Not very active community.

Summary: I recommend to use it once, I guess you will consider to that for the future in daily work load. Secondly, I you can access their articles also.

Positive: Easy to handle, support available, Integration with others possible, Handy as well as compared to the others.

Negative: Not really familiar in the market as per the current trending list.

Summary: Overall, it's a good product still growing in features and questionable for critical use cases.
While ease of setup/use/admin is strong points, limitations arise when we hit issues and being unable to figure out root cause or troubleshoot.
In many cases, just have to wait it out so it can resolve on its own. In many cases when db goes into a toss, unable to connect and/or run any commands in the DB.
Log spews out too much information. In a heavy used system doing tons of transactions/statements continuously, its just overwhelming to find something in the log especially when troubleshooting an issue. Maybe if could separate system and non-system (eg DML statements) into separate logs.

Positive: -Ease of install
-Easy replica set setup
-Ease of administration
-Pretty quick support assistance most of the time

Negative: -Limitations for VLDB in respect to acceptable backup runtime
-Limited debug/troubleshooting options
-Still seems a product in infancy