Cloudant is an open source non-relational, distributed database service that requires zero-configuration. It's based on the Apache-backed CouchDB project and the creator of the open source BigCouch project.
Cloudant's service provides integrated data management, search, and analytics engine designed for web applications. Cloudant scales your database on the CouchDB framework and provides hosting, administrative tools, analytics and commercial support for CouchDB and BigCouch.
Cloudant is often…
$1
per month per GB of storage above the included 20 GB
Cray Graph Engine (CGE), discontinued
Score 0.0 out of 10
N/A
The Cray Graph Engine (CGE) lets the user analyze data using pattern matching and filtering, sophisticated graph algorithms and analysis, in an interactive system that scales to graphs with billions of edges. It is not supported since the acquisition of Cray by HPE in 2019.
N/A
Google BigQuery
Score 8.7 out of 10
N/A
Google's BigQuery is part of the Google Cloud Platform, a database-as-a-service (DBaaS) supporting the querying and rapid analysis of enterprise data.
$6.25
per TiB (after the 1st 1 TiB per month, which is free)
Pricing
IBM Cloudant
Cray Graph Engine (CGE), discontinued
Google BigQuery
Editions & Modules
Standard
$1
per month per GB of storage above the included 20 GB
Standard
$75
per month 100 reads/second ; 50 writes/second ; 5 global queries/second
Lite
Free
20 reads/second ; 10 writes/second ; 5 global queries / second ; 1 GB of storage capacity
Google BigQuery is less expensive to run and offers free storage of up to the first 10 GB of data. Google BigQuery is also easier (and faster) to get up and running. Unlike Snowflake, Google BigQuery does not require any manual scaling or performance tuning. Scaling is …
Our organization found Cloudant most suitable if One, a fixed pricing structure would make the most sense, for example in a situation where the project Cloudant is being used in makes its revenue in procurement or fixed retainer — thus the predictability of costs is paramount; Two, where you need to frequently edit the data and/or share access to the query engine to non-engineers — this is where the GUI shines.
Event-based data can be captured seamlessly from our data layers (and exported to Google BigQuery). When events like page-views, clicks, add-to-cart are tracked, Google BigQuery can help efficiently with running queries to observe patterns in user behaviour. That intermediate step of trying to "untangle" event data is resolved by Google BigQuery. A scenario where it could possibly be less appropriate is when analysing "granular" details (like small changes to a database happening very frequently).
GSheet data can be linked to a BigQuery table and the data in that sheet is ingested in realtime into BigQuery. It's a live 'sync' which means it supports insertions, deletions, and alterations. The only limitation here is the schema'; this remains static once the table is created.
Seamless integration with other GCP products.
A simple pipeline might look like this:-
GForms -> GSheets -> BigQuery -> Looker
It all links up really well and with ease.
One instance holds many projects.
Separating data into datamarts or datameshes is really easy in BigQuery, since one BigQuery instance can hold multiple projects; which are isolated collections of datasets.
Please expand the availability of documentation, tutorials, and community forums to provide developers with comprehensive support and guidance on using Google BigQuery effectively for their projects.
If possible, simplify the pricing model and provide clearer cost breakdowns to help users understand and plan for expenses when using Google BigQuery. Also, some cost reduction is welcome.
It still misses the process of importing data into Google BigQuery. Probably, by improving compatibility with different data formats and sources and reducing the complexity of data ingestion workflows, it can be made to work.
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
We have to use this product as its a 3rd party supplier choice to utilise this product for their data side backend so will not be likely we will move away from this product in the future unless the 3rd party supplier decides to change data vendors.
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.
I think overall it is easy to use. I haven't done anything from the development side but an more of an end user of reporting tables built in Google BigQuery. I connect data visualization tools like Tableau or Power BI to the BigQuery reporting tables to analyze trends and create complex dashboards.
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.
I have never had any significant issues with Google Big Query. It always seems to be up and running properly when I need it. I cannot recall any times where I received any kind of application errors or unplanned outages. If there were any they were resolved quickly by my IT team so I didn't notice them.
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.
I think Google Big Query's performance is in the acceptable range. Sometimes larger datasets are somewhat sluggish to load but for most of our applications it performs at a reasonable speed. We do have some reports that include a lot of complex calculations and others that run on granular store level data that so sometimes take a bit longer to load which can be frustrating.
BigQuery can be difficult to support because it is so solid as a product. Many of the issues you will see are related to your own data sets, however you may see issues importing data and managing jobs. If this occurs, it can be a challenge to get to speak to the correct person who can help you.
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
The feature-set, including security, is very comparable. Overall, IBM's services added to the product are mature and stable, although product support and engineers could be a little better. Global availability is improving, and Disaster Recover Capabilities are great. Overall, it's very comparable to MongoDB as a DBaaS offer, available globally and with great documentation.
PowerBI can connect to GA4 for example but the data processing is more complicated and it takes longer to create dashboards. Azure is great once the data import has been configured but it's not an easy task for small businesses as it is with BigQuery.
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.
We have continued to expand out use of Google Big Query over the years. I'd say its flexibility and scalability is actually quite good. It also integrates well with other tools like Tableau and Power BI. It has served the needs of multiple data sources across multiple departments within my company.
Google Support has kindly provide individual support and consultants to assist with the integration work. In the circumstance where the consultants are not present to support with the work, Google Support Helpline will always be available to answer to the queries without having to wait for more than 3 days.
Previously, running complex queries on our on-premise data warehouse could take hours. Google BigQuery processes the same queries in minutes. We estimate it saves our team at least 25% of their time.
We can target our marketing campaigns very easily and understand our customer behaviour. It lets us personalize marketing campaigns and product recommendations and experience at least a 20% improvement in overall campaign performance.
Now, we only pay for the resources we use. Saved $1 million annually on data infrastructure and data storage costs compared to our previous solution.