IBM Cloudant vs. Firebase

IBM Cloudant is the best implementation of CouchDB, or any NoSQL database that you could use if you are looking for a database that can handle extremely rapid writes to a database without having to worry about transactional integrity. IBM Cloudant also abstracts out CouchDB's replication/multi-node requirements and ensures high availability on its own. It also allows map-reduce based indexing which will allow massive databases to be aggregated and queried very quickly. It should not be used in cases where you require structured data which is organized according to a schema, or if you want to maintain ACID database properties.

Incentivized

Firebase should be your first choice if your platform is mobile first. Firebase's mobile platform support for client-side applications is second to none, and I cannot think of a comparable cross-platform toolkit. Firebase also integrates well with your server-side solution, meaning that you can plug Firebase into your existing app architecture with minimal effort.

Firebase lags behind on the desktop, however. Although macOS support is rapidly catching up, full Windows support is a glaring omission for most Firebase features. This means that if your platform targets Windows, you will need to implement the client functionality manually using Firebase's web APIs and wrappers, or look for another solution.

Incentivized

• We had a small data mart project that required the storage of some rather highly connected data that also had a relatively small footprint. This made IBM Cloudant an obvious choice because we could store the data in a data structure that met our project need al while using a platform that our web development team understood and was comfortable with.
• We had a bunch of geospatial data that we needed for analysis. Having GeoJSON being natively supported by Cloudant made it an easy choice.
• Cloudant was cloud-based and didn't require a DBA support it, this allowed the project to move ahead without pushback from the infrastructure team.

Incentivized

• Extremely robust. Has about any tool you can think of under one roof making it extremely useful as a backup platform for data analytics or small teams that need something quickly.
• Intuitive and easy UI/UX. Being made and owned by Google, you expect nothing less. Very easy to use for anyone that has any marketing or analytical experience especially in Google Analytics (which I just assume all marketers do).
• Safe, secure, and sturdy. Never need to worry about downtimes or misinformation as it's as clean and safe as it is being run by Google.
• FREE! What else is there to say. Unless you're an extremely large application handling hundreds of thousands to millions of users, this pay as you go plan will stay free.

Incentivized

• To have a sort of LUW - Logical Unit Work when many documents are involved into a single update process. The changing of one document is related to its status information but it must be synchronized with all the other documents involved in the process.

Incentivized

• Firebase/Firestore has very limited support for querying more complicated items; for example, performing a simple string search is not possible.
• While upfront costs are low, costs can grow quickly if you're not careful about what you are being billed for.
• Dashboards have at times shown different information to what is billed, and support from Google is less than stellar and not as effective as that from Amazon or Microsoft.

Incentivized

the flexibility of NoSQL allow us to modify and upgrade our apps very fast and in a convenient way. Having the solution hosted by IBM is also giving us the chance to focus on features and the improvement of our apps. It's one thing less to be worried about

Incentivized

It's mostly just a straight forward API to a data store. I knock one off for the full text search thing, but I don't need it much anyways. Also, the dashboard UI they give is pretty nice to use. It provides syntax-highlighting for writing views and queries are easy to test. I wish other DBs had a UI like this.

Incentivized

I don't use the Firebase UI much, but rather connect it to GA4. GA4 has a great event model but the GA4 UI and analysis capabilities are limited. It's harder to measure product usage type of engagement but if you have the time and resources to leverage the GA4 to BiqQuery export you'll have all the raw event data you'll need for deep analysis, segmentation, and audience activation.

Incentivized

it is a highly available solution in the IBM cloud portfolio and hence we have never had any issues with the data base being available - we also do continuous replication to be on the safer side just in case some thing goes awry. We also perform twice a year disaster recovery tests.

Incentivized

very easy to get started and is very developer friendly given that it uses couchDB analytics. It is a cloud based solution and hence there is no hardware investment in a server and staging the server to get started and the associated delays/bureaucracy involved to get started. Good documentation is also available.

Incentivized

Very happy by the commitment given by the team which has been really good over the last 7 years of usage.

Incentivized

Our analytics folks handled the majority of the communication when it came to customer service, but as far as I was aware, the support we got was pretty good. When we had an issue, we were able to reach out and get support in a timely fashion. Firebase was easy to reach and reasonably available to assist when needed.

Incentivized

online resources are good enough to understand but there is nothing like testing. In our case, we discovered some not documented behavior that we take in count now. Also, the experience in NodeJs is critical. Also, take in count that most of the "good practices" with cloudant are not in online courses but in blogs and pages from independent developers

Incentivized

• Test the architecture on CouchDB helped us to address initial design flaws.
• The migration to Cloudant as such was very painless.
• We have migrate our replication system to Cloudant Android Sync for mobile devices.
• We have regular informal contact with the Cloudant leadership to discuss our use cases and implementation strategies.

Incentivized

MongoDB Atlas and Azure Cosmos DB are the closest competitors we found with Cloudant, especially in terms of fixed pricing and having a GUI for easy viewing and quick edits of data. Cloudant's pricing model flat out beats MongoDB Atlas' in terms of how easy it would be to predict costs. Cosmos DB is a much closer competitor, as it integrates well with Azure's stack similarly to Cloudant and the rest of the IBM Cloud stack; similar [throughout]-based pricing and replication options; and even the GUI and ease of query using SQL, which my team and I were more familiar with. Where Cloudant beats out Cosmos DB is again having a more simple pricing model (ops/sec vs Cosmos' "request units" voodoo) and being based on open-source software assuaging fears of vendor lock-in.

Incentivized

Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted database. This simplicity has allowed us to try features that we might not have based on the amount of work they required in the past.

Incentivized

The service scales incredibly well. As you would expect from CloudDB and IBM combination. The only reason I wouldn't score it a 10 is the fact that document trees can get nested and nested very quickly if you are attempting to do very complex datasets. Which makes your code that much more complex to deal. Its very possible we could find a solution to this problem with better database planning to begin with, but one of the reasons we chose a service over a self-hosted solution was so we could set it up quick and forget about it. So we weren't going to dedicate a team to architecture optimization.

Incentivized

• Saving in-terms of cost of procuring and maintaining hardware, which will be realized over the next 5 years.
• Positive ROI in terms of the number of FTEs involved in maintaining our databases; our DBAs can now focus on other important and business critical applications.
• Best ROI in terms of our organization's vision - they are no longer anxious / nervous to move to the cloud. We are already on the CLOUD.

Incentivized

• Firebase has been able to help us understand reliably, the drop-off in our user flows with their funnel feature. This has made it easy for us to be able to pinpoint weaknesses in our funnel and test and optimize with data as the dependent variable.
• From an economic standpoint, we don't pay for Firebase which is great, but as the saying goes "You get what you pay for" also holds true in this context. As we looked to grow and scale, we looked for a paid solution.
• From a developer resource standpoint, Firebase has been extremely easy to integrate into our app. Whether it be the event tracking, dynamic links or crash reporting we have not had to waste too much developer time thanks to their well-organized developer docs.

Incentivized