Apache Cassandra vs. MongoDB vs. Quickbase

Apache Cassandra is a NoSQL database and well suited where you need highly available, linearly scalable, tunable consistency and high performance across varying workloads. It has worked well for our use cases, and I shared my experiences to use it effectively at the last Cassandra summit! http://bit.ly/1Ok56TK It is a NoSQL database, finally you can tune it to be strongly consistent and successfully use it as such. However those are not usual patterns, as you negotiate on latency. It works well if you require that. If your use case needs strongly consistent environments with semantics of a relational database or if the use case needs a data warehouse, or if you need NoSQL with ACID transactions, Apache Cassandra may not be the optimum choice.

Incentivized

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.

Incentivized

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.

Incentivized

• Continuous availability: as a fully distributed database (no master nodes), we can update nodes with rolling restarts and accommodate minor outages without impacting our customer services.
• Linear scalability: for every unit of compute that you add, you get an equivalent unit of capacity. The same application can scale from a single developer's laptop to a web-scale service with billions of rows in a table.
• Amazing performance: if you design your data model correctly, bearing in mind the queries you need to answer, you can get answers in milliseconds.
• Time-series data: Cassandra excels at recording, processing, and retrieving time-series data. It's a simple matter to version everything and simply record what happens, rather than going back and editing things. Then, you can compute things from the recorded history.

Incentivized

• 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.

Incentivized

• Rapidly bring new ideas to life
• Great authentication and authorization system out of the box
• Connects with many major third-party services (via Pipelines)
• Reporting and Dashboards are awesome
• Excellent emails notification system to keep us in the loop when data changes
• Intuitive UI for building forms and reports
• Nice playground to test new ideas

Incentivized

• Cassandra runs on the JVM and therefor may require a lot of GC tuning for read/write intensive applications.
• Requires manual periodic maintenance - for example it is recommended to run a cleanup on a regular basis.
• There are a lot of knobs and buttons to configure the system. For many cases the default configuration will be sufficient, but if its not - you will need significant ramp up on the inner workings of Cassandra in order to effectively tune it.

Incentivized

• 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.

Incentivized

• 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.

Incentivized

I would recommend Cassandra DB to those who know their use case very well, as well as know how they are going to store and retrieve data. If you need a guarantee in data storage and retrieval, and a DB that can be linearly grown by adding nodes across availability zones and regions, then this is the database you should choose.

Incentivized

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.

Incentivized

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.

Incentivized

It’s great tool but it can be complicated when it comes administration and maintenance.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

Sometimes instead giving straight answer, we ‘re getting transfered to talk professional service.

Incentivized

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.

Incentivized

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.

It is very easy to get training from their University portal and still if we don't know their, then we can ask their support too.

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.

Incentivized

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 evaluated MongoDB also, but don't like the single point failure possibility. The HBase coupled us too tightly to the Hadoop world while we prefer more technical flexibility. Also HBase is designed for "cold"/old historical data lake use cases and is not typically used for web and mobile applications due to its performance concern. Cassandra, by contrast, offers the availability and performance necessary for developing highly available applications. Furthermore, the Hadoop technology stack is typically deployed in a single location, while in the big international enterprise context, we demand the feasibility for deployment across countries and continents, hence finally we are favor of Cassandra

Incentivized

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.

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.

Incentivized

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.

Incentivized

For clients we use Qucik base to develop application

Incentivized

• I have no experience with this but from the blogs and news what I believe is that in businesses where there is high demand for scalability, Cassandra is a good choice to go for.
• Since it works on CQL, it is quite familiar with SQL in understanding therefore it does not prevent a new employee to start in learning and having the Cassandra experience at an industrial level.

Incentivized

• 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

• 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