MongoDB is an open source document-oriented database system. It is part of the NoSQL family of database systems. Instead of storing data in tables as is done in a "classical" relational database, MongoDB stores structured data as JSON-like documents with dynamic schemas (MongoDB calls the format BSON), making the integration of data in certain types of applications easier and faster.
$0.10
million reads
PostgreSQL
Score 8.5 out of 10
N/A
PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.
N/A
Pricing
MongoDB
PostgreSQL
Editions & Modules
Shared
$0
per month
Serverless
$0.10million reads
million reads
Dedicated
$57
per month
No answers on this topic
Offerings
Pricing Offerings
MongoDB
PostgreSQL
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Fully managed, global cloud database on AWS, Azure, and GCP
Looking into PostgreSQL happened post move to Mongo. Had we considered both options at the time we likely would have went with PostgreSQL. We may migrate at some point in the future but currently it doesn't make sense.
We have [measured] the speed in reading/write operations in high load and finally select the winner = MongoDBWe have [not] too much data but in case there will be 10 [times] more we need Cassandra. Cassandra's storage engine provides constant-time writes no matter how big your …
Both Couchbase and MongoDB are document-oriented NoSQL databases, so they have very similar features. While they do have some fundamental differences in terms of how they scale, shard, etc. the one key reason why we went with MongoDB is its availability and support from the …
The flexible structure underlying MongoDB's construction is not found in other competitors; the ability to easily change the structure without affecting other stored documents. It is very ideal for projects that you cannot predict that the structure will change this way. Of …
MongoDB is our go-to database solution for any project, and the more we work with it the more we love it. Some say that NoSQL is pointless... Our developers wholeheartedly disagree, because they love working with it. Though both NoSQL and SQL have their purposes, in most …
Your default choice should not be MongoDB in my opinion. Most user-facing systems are relational by nature so a well known and reliable SQL database would be easier to maintain and simpler to develop long term. If you highly value speed of development go with Firebase. If you …
We tend to choose MongoDB when we're faced with a particular situation: we know that we need a NoSQL database in general, and want an open-source implementation that allows us to prevent against platform lock-in. Amazon's new DocumentDB product even allows us to choose to use …
MongoDB is the best NoSQL database out there. There are others, but Mongo has the largest community, is very easy to set up, and is extremely performant. Compared to a relational DB (like MySQL or Postgres) is like comparing apples and oranges. One isn't better or worse than …
I recently tried out Firestore from the Google firebase family of development products. While it allows structuring of data similar to MongoDB, it handles things a little differently. MongoDB documents are incredibly flexible and can be structured really any way you can …
MongoDB is my only NoSQL database that I have used. I have used SQL databases and don't find them as enjoyable. I code in full stack JavaScript and it blends perfectly with this. I know that there are competitors in this space, and I need to take time to try them all out. I …
I selected MongoDB because it works for well with web interfaces. All of the RDBMS alternatives would have required a lot more time writing schemas and working around retrieving data and mapping it. That could have been somewhat mitigated with Entity Framework, but that again …
The features between these database are quite comparable - except for possibly MongoDB. MongoDB being a different type of database and geared towards big data - I don't compare it to PostgreSQL. The other two I have used and would say PostgreSQL does fairly well when compared …
Despite being all open source options, what ended up making us choose PostgreSQL was the robustness of its core, which allows the great workflow that can support timely and efficient response to the demand and demand for resources. In the case of MongoDB, it is a non-relational …
MySQL is a popular open-source alternative to PostgreSQL, but in my experience it lacks the robustness, durability, and flexibility of PostgreSQL. It has also changed hands frequently, so support isn't the greatest. MongoDB and other NoSQL databases are helpful in certain …
First It's open source and it's cost-effective compared to other databases.PostgreSQL can be easily integrated with numerous platforms. It is well known and appreciated so relying on it as our system database can be easily accepted by our customers. And if your developing a …
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale. SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows …
When we were originally evaluating Redshift we ran into some issue with dates. Either way, Postgres is a better choice than Redshift because it avoids vendor lockin. We ended up choosing Postgres over MySQL because it was easier at the time to get a hosted Postgres cluster up …
Much more mature and stable when compared to MySQL with features such as MVCC, complex subquery plans, ORDBMS, and NoSQL support. With Oracle retaining rights to MySQL its future as an open database is less secure and is no longer in the hands of the community. PostgreSQL also …
We selected PostgreSQL due to the number of employees who have used it in the past. The data consistency guarantees. The multiple transaction isolation levels support.
PostgreSQL outperforms every other option. It is faster, more flexible, more reliable, easier to maintain, and more consistent in behaviour than any of the other offerings.
It's a viable alternative, with a rich feature set and a reliable system. PostgreSQL is one of the best RDBMS's currently on the market in 2020, it serves just as well as a starter, PoC DB for any software idea as a final, highly valuable database solution for big systems.
PostgreSQL is the proper tool when data consistency matters and other BASE or document-based databases are simply improper. I think PostgreSQL has a fantastic system of slony replication, triggers, and other data maintenance functionality that other databases generally don't …
Compared to MySQL, it works well if you need to extend to your use case Compared to Spark, it works better w.r.t development time in a central database setting Like Redis, it cannot be used for caching and quick access of non-structured data
As I said, Postgres and MySQL are open source which is important for small start ups. Oracle is EXPENSIVE :) Postgres is faster than MySQL (Big factor) MySQL supports replication which makes it more scalable.
I am currently using MySQL and it is difficult to notice much of a difference at all. For free relational databases, there hasn't been enough for me to choose a clear winner. If you're already using a free solution, there would be no reason to change. In terms of comparing to a …