However, while MongoDB and PostgreSQL are actually quite different from one another, HarperDB lies somewhere in the middle.Īs mentioned, there are numerous resources out there comparing MongoDB and PostgreSQL, which are both awesome databases. These technologies are all similar in that they are used to store data, but that simple concept is where the similarities end. That article provides a great high-level explanation across all different types of databases, but today, we’ll get a but more specific. Referring to my database architecture overview post again: It’s important to understand things such as data type/structure, data volume, consistency, write and read frequency, hosting, cost, security, and integration constraints. However, with HarperDB being a net new database, I thought it might be helpful to throw it in the mix to provide further clarity. With MongoDB and PostgreSQL being two of the most popular tools out there, you may already know that there are tons of resources comparing the two. The point of this article is not to determine which database is the best, but to help uncover the factors to consider when selecting a database for your specific project. So today let’s do a comparison of three different database systems.Īs stated in my Database Architectures and Use Cases article: In most cases, it’s not that one database is better than the other, it’s that one is a better fit for a specific use case due to numerous factors. When it comes to products and technology, a lot of people ask “how are you different,” but different from what? You need some sort of baseline to start from, so you can say, “Similar to X, but different because of Y.” Because of this, comparisons, competitive analysis, and feature matrices are a great way to understand which technology solutions are right for you.

This makes sense, it’s probably a natural instinct. Many people learn or understand new things relative to things they already know.

Mongodb vs postgresql