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.7 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
Toad Database Developer Tools
Score 8.8 out of 10
N/A
Toad by Quest is a database management toolset that database developers, administrators and data analysts use to simplify workflows, create code free from defects, automate frequent or repetitive processes, and minimize risks. Editions include Toad for Oracle, which automates administration tasks and helps proactively manage databases while embracing performance optimization and risk mitigation. Similar editions exist for IBM DB2, SQL Server, SAP, or MySQL and Postgres environments (Toad Edge).
$229
per year
Pricing
MongoDB
PostgreSQL
Toad Database Developer Tools
Editions & Modules
Shared
$0
per month
Serverless
$0.10million reads
million reads
Dedicated
$57
per month
No answers on this topic
Toad Edge For MySQL
$229
per year
Toad Edge For Postgres
$229
per year
Toad for SQL - Pro Edition
$437
per year
Toad for Oracle - Base Edition
$550
per year
Toad for DB2 z/OS - Base Edition
$636
per year
Toad for SAP - Base Edition
$636
per year
Toad for SQL - Xpert Edition
$763
per year
Toad for Oracle - Professional Edition
$829
per year
Toad for SQL - Dev Edition
$930
per year
Toad for DB2 z/OS - Pro Edition
$996
per year
Toad for Oracle - Professional DB Admin Edition
$1,370
per year
Toad for DB2 z/OS - Xpert Edition
$1,529
per year
Toad for SAP - Xpert Edition
$1530
per year
Toad for Oracle - Xpert Plus Edition
$1,753
per year
Toad for DB2 z/OS - Dev Edition
$1,861
per year
Toad for SAP - Dev Edition
$1863
per year
Toad for SAP - Xpert+ Edition
$2099
per year
Toad for SAP - DBA Edition
$3661
per year
Offerings
Pricing Offerings
MongoDB
PostgreSQL
Toad Database Developer Tools
Free Trial
Yes
No
Yes
Free/Freemium Version
Yes
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No 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 …
If asked by a colleague I would highly recommend MongoDB. MongoDB provides incredible flexibility and is quick and easy to set up. It also provides extensive documentation which is very useful for someone new to the tool. Though I've used it for years and still referenced the docs often. From my experience and the use cases I've worked on, I'd suggest using it anywhere that needs a fast, efficient storage space for non-relational data. If a relational database is needed then another tool would be more apt.
PostgreSQL is best used for structured data, and best when following relational database design principles. I would not use PostgreSQL for large unstructured data such as video, images, sound files, xml documents, web-pages, especially if these files have their own highly variable, internal structure.
Toad for Oracle is very well suited for all Oracle implementations, be it single instance or RAC. It is best suited for use of Oracle DBA, Developer and Database Engineers. I don't recommend Toad for Oracle for Project Managers or Solution Architects. This can be a pricier choice for these people. They can do fine with free options like SQL Developer.
Being a JSON language optimizes the response time of a query, you can directly build a query logic from the same service
You can install a local, database-based environment rather than the non-relational real-time bases such a firebase does not allow, the local environment is paramount since you can work without relying on the internet.
Forming collections in Mango is relatively simple, you do not need to know of query to work with it, since it has a simple graphic environment that allows you to manage databases for those who are not experts in console management.
Toad is a de-facto standard tool for data developers and analysts. Generally speaking it provides almost every function needed to manage data in EDW with great performance and stability.
The nature of clinical data is big-sized: one table may have billions of rows. Toad provides critical functions to manage SQLs, e.g. Top SQL that can monitor and manage SQLs using CPU power and network bandwidth, so that EDW administrator can optimize ETL operations in the best efficiency.
Many of our data analysts are not computer science backgrounded (having clinical / nursing background). Toad provides great auditing tools such as Tuning Lab or SQL Scanner, so that data analysts can train themselves with guidance of the tool.
An aggregate pipeline can be a bit overwhelming as a newcomer.
There's still no real concept of joins with references/foreign keys, although the aggregate framework has a feature that is close.
Database management/dev ops can still be time-consuming if rolling your own deployments. (Thankfully there are plenty of providers like Compose or even MongoDB's own Atlas that helps take care of the nitty-gritty.
The power and control it gives is at the same time kind of a negative thing. There's too many options available, even when you don't need them. For simple database operations it's sometimes easier to just use SQL Developer since navigation is way more intuitive and easy.
Related with the above: there is a steep learning curve. However, since this is the main tool for any Oracle developer, this is not that much of a problem.
If I remember well, Toad used to be free, some 20 years ago. Or at least had a free version. It would be nice to have a free version. The dedicated Oracle developers and DBA's won't use the free version, but all the rest of us developers might use it instead of SQL Developer. It would make communications between everybody somewhat easier.
I am looking forward to increasing our SaaS subscriptions such that I get to experience global replica sets, working in reads from secondaries, and what not. Can't wait to be able to exploit some of the power that the "Big Boys" use MongoDB for.
NoSQL database systems such as MongoDB lack graphical interfaces by default and therefore to improve usability it is necessary to install third-party applications to see more visually the schemas and stored documents. In addition, these tools also allow us to visualize the commands to be executed for each operation.
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
I give is an 8 because nothing is a 10 and there is always room for improvement. I believe the user who is not as technologically inclined would be better suited with an easier way to identify the options for setting the layout up for Toad's GUI. To some it is very cumbersome and confusing.
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
Finding support from local companies can be difficult. There were times when the local company could not find a solution and we reached a solution by getting support globally. If a good local company is found, it will overcome all your problems with its global support.
There are several companies that you can contract for technical support, like EnterpriseDB or Percona, both first level in expertise and commitment to the software.
But we do not have contracts with them, we have done all the way from googling to forums, and never have a problem that we cannot resolve or pass around. And for dozens of projects and more than 15 years now.
I give the overall support for Toad for Oracle a 10/10. This is because whenever there has been an issue with this software, our team has got an immediate response. The same can not be said for similar software. The most recent example of this is when we needed to renew our licenses. Some employees were unable to log in to code with the given license key. Support was able to resolve the issue quickly.
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
While the setup and configuration of MongoDB is pretty straight forward, having a vendor that performs automatic backups and scales the cluster automatically is very convenient. If you do not have a system administrator or DBA familiar with MongoDB on hand, it's a very good idea to use a 3rd party vendor that specializes in MongoDB hosting. The value is very well worth it over hosting it yourself since the cost is often reasonable among providers.
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 data set grows. For analytics, MongoDB provides a custom map/reduce implementation; Cassandra provides native Hadoop support.
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same family of applications that performs the company that develops it and that is not all bad, but being able to adapt or configure different programs, applications or other environments developed by third parties apart is what gives PostgreSQL a certain advantage and this diversification in the components that can be joined with it, is the reason why it is a great option to choose.
Toad is much better than Tableau query writer. Tableau is not intuitive and requires knowledge of proprietary database language to fully implement. Tableau does not perform as quickly and accurately as Toad. Toad is very easy and slim to install. Additional hardware is often required to run Tableau smoothly. Support for Tableau is even more expensive than Toad support.
Open Source w/ reasonable support costs have a direct, positive impact on the ROI (we moved away from large, monolithic, locked in licensing models)
You do have to balance the necessary level of HA & DR with the number of servers required to scale up and scale out. Servers cost money - so DR & HR doesn't come for free (even though it's built into the architecture of MongoDB
Easy to administer so our DevOps team has only ever used minimal time to setup, tune, and maintain.
Easy to interface with so our Engineering team has only ever used minimal time to query or modify the database. Getting the data is straightforward, what we do with it is the bigger concern.
Quick and easy query development helps reduce man-hours in a project which converts to real dollars.
Query analysis and tuning result in low database overhead and low latency, thus translating into real dollars because a system can thus handle more requests from customers.
Ease of use makes it easy to deploy greenhorns in projects with minimal training, thus helping save money. Otherwise menial and simple jobs would have required experienced DBAs.