MongoDB Atlas vs. Percona Server

I would recommend MongoDB Atlas to every company who have a significant need in the NoSQL database and do not want to manage their infrastructure. Using MongoDB Atlas can significantly reduce your management time and cost, which saves valuable resources for other tasks. It also suits a smaller company as MongoDB Atlas scales up and down very quickly.

Incentivized

It is a good tool to carry out tests that measure the level of effectiveness of the database and it behaves well when, at the project level, we need to process large volumes of data in a massive way. It is not an optimal solution for applications oriented to the distribution of data between different machines.

Incentivized

• Generous free and trial plan for evaluation or test purposes.
• New versions of MongoDB are able to be deployed with Atlas as soon as they're released—deploying recent versions to other services can be difficult or risky.
• As the key supporters of the open source MongoDB project, the service runs in a highly optimized and performant manner, making it much easier than having to do the work internally.

Incentivized

• Feature Rich: Percona Server for MySQL always has some additional features on top of MySQL.
• Performance improvements: Additional performance
• Integration with Native and Community tooling: It supports all native and community developed tooling for MySQL

• For someone new, it could be challenging using MongoDB Atlas. Some official video tutorials could help a lot
• Pricing calculation is sometimes misleading and unpredictable, maybe better variables could be used to provide better insights about the cost
• Since it is a managed service, we have limited control over the instances and some issues we faced we couldn't;'t know about without reaching out to the support and got fixed from their end. So more control over the instance might help
• The way of managing users and access is somehow confusing. Maybe it could be placed somewhere easy to access

Incentivized

• A distributed database offering to scale writes with native sharding. Currently we make use of sharding managed by the application to scale writes. There is the option to place ProxySQL in front of the shards, but we need a true cloud native distributed option with an easy migration path. I would not say this is negative in terms of Percona Server for MySQL, but if Percona had a distributed database offering at some stage, we would follow Percona.

I would give it 8. Good stuff: 1. Easy to use in terms of creating cluster, integrating with Databases, setting up backups and high availability instance, using the monitors they provide to check cluster status, managing users at company level, configure multiple replicas and cross region databases. Things hard to use: 1. roles and permissions at DB level. 2. Calculate expected costs

Incentivized

Good community support.

We love MongoDB support and have great relationship with them. When we decided to go with MongoDB Atlas, they sent a team of 5 to our company to discuss the process of setting up a Mongo cluster and walked us through. when we have questions, we create a ticket and they will respond very quickly

Incentivized

We are using opensource so we have not used customer support.

In general, they all compete against each other, and each solution has its own advantages and disadvantages. While MongoDB Atlas was the way to go for some cases, however, other databases were more fit for some services that MongoDB Atlas, especially if they were managed by us, which means less cost, like Redis for example

Incentivized

Performance and stability sets Percona Server for MySQL apart from the rest. Percona embraces the upstream version and contributes towards the upstream version making MySQL stronger on two fronts and thus having a much larger community. Many quality contributions have been made by Percona into the base code. Percona provides great tools to support Percona Server for MySQL and this makes the monitoring and management easier

• Positive - Faster provisioning so we don't have development teams waiting.
• Positive - Automated backups and server management - eliminates need for dedicated DBAs.

Incentivized

• Increased efficiency with faster querying
• Easy scalability