Skip to content

Commit f437d48

Browse files
authored
Update cosmos-db-vs-mongodb-atlas.md
1 parent 35a60ef commit f437d48

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cosmos-db/mongodb/cosmos-db-vs-mongodb-atlas.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ ms.date: 02/27/2024
3434
| Independent scaling for throughput and storage | Yes, with RU-based Azure Cosmos DB for MongoDB | No |
3535
| Vector Search for AI applications | Yes, with [vCore-based Azure Cosmos DB for MongoDB](./vcore/vector-search.md) | Yes, with MongoDB Atlas dedicated instances |
3636
| Integrated text search, geospatial processing | Yes | Yes |
37-
| Free tier | [1,000 request units (RUs) and 25 GB storage forever](../try-free.md). Prevents you from exceeding limits if you want. Azure Cosmos DB for MognoDB vCore offers Free Tier with 32GB storage forever. | Yes, with 512 MB storage |
37+
| Free tier | [1,000 request units (RUs) and 25 GB storage forever](../try-free.md). Prevents you from exceeding limits if you want. vCore-based Azure Cosmos DB for MongoDB offers Free Tier with 32GB storage forever. | Yes, with 512 MB storage |
3838
| Live migration | Yes | Yes |
3939
| Azure Integrations | [Native first-party integrations with Azure services](./integrations-overview.md) | Third party integrations, including some native Azure services |
4040
| Choice of instance configuration | Yes, with [vCore-based Azure Cosmos DB for MongoDB](./vcore/introduction.md) | Yes |

0 commit comments

Comments
 (0)