YugabyteDB now offers a MongoDB-compatible API with the support of the DocumentDB PostgreSQL extension, providing developers with an open source alternative for MongoDB workloads that need to scale horizontally. Follow this step-by-step guide to deploying and running MongoDB workloads on YugabyteDB in collaboration with Microsoft (DocumentDB) and FerretDB.
Data migration can be a complex and time-consuming task, but proper planning can help streamline the process. In this blog, we’ll demonstrate how to migrate a Sakila demo database from MongoDB to a YugabyteDB cluster using Studio 3T, highlighting the key steps and considerations involved in the process.
In this post, we comparethe high availability and transactions architecture of PostgreSQL and MongoDB to that of YugabyteDB.
In this post, we reviewed the building blocks of the YugabyteDB and mapped them to the corresponding concepts (if any) in PostgreSQL and MongoDB.
The SQL vs. NoSQL database split emerged in 2006-2007, but NoSQL’s compromises led developers to continue using SQL/RDBMS for critical workloads. However, recent changes in the NoSQL world have seen the adoption of ACID transactions, which were previously absent, and this post aims to inform architects of these changes and why they are happening now.
MongoDB’s “schemaless” JSON data modeling was initially attractive to web app developers looking to escape the constraints of traditional relational databases, but issues with data durability and ACID transactions have been a consistent challenge. While the recent MongoDB 4.0 release includes multi-document transaction support, this post explores where the platform falls short for transactional, high performance apps.
This post delves into the technical requirements of fast-growing geo-distributed applications with low latency reads and explores the limitations of Amazon DynamoDB for this use case, as well as alternative solutions such as MongoDB, Apache Cassandra, and YugabyteDB, a high-performance distributed SQL database.
