CompaniesDatabricksvs MongoDB Atlas
Databricks vs MongoDB Atlas
From vendor reports Category: data. Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.
| Databricks | MongoDB Atlas | |
|---|---|---|
| Free of major/critical incidents, 30 days | 98.78% | 100% |
| Free of major/critical incidents, 90 days | 99.37%* | 98.26% |
| Free of any incident, 90 days | 99.28% | 97.29% |
| Outage time (major/critical), 90 days | 11 h 55 min | 37 h 26 min |
| Incidents started, 30 days | 2 | 1 |
| Incidents started, 90 days | 6 | 8 |
| Silently edited or deleted incidents (all time / 90 days) | 0 / 0 | 1 / 1 |
| Price changes detected | 0 | 0 |
| Deprecations and breaking changes | 14 | 5 |
| CVEs mapped to the vendor | 0 | 296 |
* Window shortened: our archive of Databricks’s status page starts .
Counts are facts from the vendors’ own pages as archived by Rewindex; impact labels are the vendors’ own. Not a ranking. Recomputed .
Databricks uptimeMongoDB Atlas uptimeSilent editsMarkdownJSON