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
Quickbase
Score 8.6 out of 10
N/A
Quickbase helps users tackle any project, no matter how complex. Quickbase helps customers see, connect and control complex projects. Whether it’s raising a skyscraper or coordinating vaccine rollouts, the no-code software platform allows business users to custom fit solutions to the way they work – using information from across the systems they already have.
$700
per month
Pricing
MongoDB
PostgreSQL
Quickbase
Editions & Modules
Shared
$0
per month
Serverless
$0.10million reads
million reads
Dedicated
$57
per month
No answers on this topic
Enterprise
Full Customizable
per month/billed annually
Business
Starting at $2,200
per month
Team
Started at $700
per month
Offerings
Pricing Offerings
MongoDB
PostgreSQL
Quickbase
Free Trial
Yes
No
Yes
Free/Freemium Version
Yes
No
No
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Optional
Additional Details
Fully managed, global cloud database on AWS, Azure, and GCP
—
Quickbase offers three key plans, with feature distinction, simple and consistent entitlements, and a flexible licensing model, giving users the option of either user based or usage based licensing across all 3 plans.
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 …
Quick Base is designed quite differently to PostgreSQL although its a database. Quick Base is a database with a front end on top. It has its limitations with capacity when compared to PostgreSQL. But this isn't its primary function.
They are much more complicated to work with. I don't have time to learn SQL or NoSQL. Quickbase takes the pain out of developing databases, optimizing, refactoring, creating elements, sizing etc... Quickbase has a much nicer user interface than what is available for the back …
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.
I no longer think that Quickbase is the way of the future. They do not fix major bugs in a timely manner, and are releasing basic functionality behind a paywall. I believe that Enterprise Level Tier should be given certain things, like SLAs on Support and up-time. However, as a low-code no-code platform the majority of the accounts, "builders", and users are not going to be able to justify the cost of an Enterprise Tier Plan, and won't be able to use the features that Quickbase continues to advertise.
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.
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.
I'd like to see a link on email notices that take you directly into said notice. On an app that only has 1 or 2 email notices firing, there's no issue. However, we have some tools that are so complex that they have about 20 email notices firing at any given time based on the action users take. In this case, if we have to go in to modify a notice, we have to guess or scroll down the long list of notices to see which one we need to customize. It would be great if Quickbase had the URL of said notice somewhere at the footer of that notice so when Administrators click on it, it takes them into the exact notice they need to update.
When filling out or reviewing a lengthy form, I'd like to see the Save & close button, as well as a Save & next option at the bottom of the form rather than having to scroll back up to the top of those forms just to click on those choices.
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.
For our use-case of QuickBase, there really aren't any other products out there that can offer us the same out-of-the-box solutions they provide to us. We're also so integrated with it in our daily processes that to move away from it abruptly would cause mass chaos, so it's going to be renewed for at least the next several years.
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.
Quick Base has done everything we have asked it to do and then some. Our original goal was to have one system for CRM that encompassed both the sales process and the customer management. We have gone w-a-y beyond that with analytics, project management, system bug logging, and historical effort reporting.
Once we did get Quick Base configured and customized it was reliably available when we needed it. We may have had one or two occasions when the product was inaccessible but those were few. The greatest challenge with its availability was its difficulty with integrating with our systems.
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.
Some of our tables that hold over a million records are starting to perform poorly, with some summaries taking over 20 seconds to load. This may be an indication that it is best to archive old data when reaching large volumes like this.
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.
If you utilize the community, the support is amazing. Unfortunately, I find their actual support system a bit underwhelming. They don't seem to have a great process for interacting directly with an issue and often sweep significant issues under the rug by categorizing them as "Enhancement" ideas or legacy items.
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.
Quick Base already is having a separate portal of providing training to customers and it is very easy to use and updates as per the new features added in to the application
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.
I was not directly involved with the initial account implementation, only a bystander. For the app I directly implemented for my department only, I wish I had know to create an app diagram first. I don't remember if that was suggested. I think that would be a great help tip tool when a new app is created, to have a page with a check list of what is needed or how to get started. If you are a regular app builder, then you can bypass it or have the ability to turn it off in the app settings.
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.
Well, there's a plethora of low-code tools out on the marketplace and, you know, there's a reason that we've decided to partner with QuickBase because it has all the right balance of the ability to integrate with the ability for a citizen developer to create apps successfully. So if you look at something like Zo Ho's low-code offering, for example, yes, there are some similarities there, but they're really dependent on all of their other licensed products to get you where you want to be, where with QuickBase you have the ability to truly create something custom.
It has evolved really well with our company, but there is a hard limit to the table size that has begun to affect us and not let us grow. The table size limit is set at 500 MB and we have had to jump through quite a few hoops to be able to get by.
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.
ROI is HUGE. Our company saved over 3.5 million in one year alone based on developments that year in Quickbase that saved time for many teams
Less user error - implementing automations and standardized workflows has led to less user error as was previously seen by maintaining spreadsheets or Smartsheets