InfluxDB vs. MongoDB Atlas

InfluxDB is very good at storing monitoring metrics (e.g. performance data). InfluxDB is not the right choice if you need to store other data types (like plain text, data relations etc.).

Incentivized

It is good if you: 1. Have unstructured data that you need to save (since it is NoSQL DB) 2. You don't have time or knowledge to setup the MongoDB Atlas, the managed service is the way to go (Atlas) 3. If you need a multi regional DB across the world

Incentivized

• Perfect handling telemetry data.
• Low latency, near real time.
• SQL-like language makes it easier to query.

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

• GUI based administrator console

Incentivized

• 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

InfluxDB is a near perfect product for time series database engines. The relatively small list of cons are heavily outweighed by it's ability to just work and be a very flexible and powerful database engine. The community and support provided by the corporation are the only areas I have little experience.

Incentivized

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

We have worked with the InfluxDB support team a few times so far and it has been positive. Issues submitted are worked on promptly and we have good feedback.

Incentivized

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

To be honest, I didn't look at alternatives since InfluxDB performs very well if you can oversee the lack of security and HA features. But for all challenges, there is an easy solution which brings you forward (e.g. read load balancing can be achieved by using a common HTTPS load balancer).

Incentivized

MongoDB is a great product but on premise deployments can be slow. So we turned to Atlas. We also looked at Redis Labs and we use Redis as our side cache for app servers. But we love using MongoDB Atlas for cloud deployments, especially for prototyping because we can get started immediately. And the cost is low and easy to justify.

Incentivized

• Provided us a time series DB.
• With the SQL-like language, it is very easy to learn.
• Empowered us to keep track of our events.

Incentivized

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

Incentivized