Need advice about which tool to choose?Ask the StackShare community!
Google BigQuery vs Google Cloud Bigtable: What are the differences?
Google BigQuery: Analyze terabytes of data in seconds. Run super-fast, SQL-like queries against terabytes of data in seconds, using the processing power of Google's infrastructure Load data with ease. Bulk load your data using Google Cloud Storage or stream it in. Easy access. Access BigQuery by using a browser tool, a command-line tool, or by making calls to the BigQuery REST API with client libraries such as Java, PHP or Python.; Google Cloud Bigtable: The same database that powers Google Search, Gmail and Analytics. Google Cloud Bigtable offers you a fast, fully managed, massively scalable NoSQL database service that's ideal for web, mobile, and Internet of Things applications requiring terabytes to petabytes of data. Unlike comparable market offerings, Cloud Bigtable doesn't require you to sacrifice speed, scale, or cost efficiency when your applications grow. Cloud Bigtable has been battle-tested at Google for more than 10 years—it's the database driving major applications such as Google Analytics and Gmail.
Google BigQuery belongs to "Big Data as a Service" category of the tech stack, while Google Cloud Bigtable can be primarily classified under "NoSQL Database as a Service".
Some of the features offered by Google BigQuery are:
- All behind the scenes- Your queries can execute asynchronously in the background, and can be polled for status.
- Import data with ease- Bulk load your data using Google Cloud Storage or stream it in bursts of up to 1,000 rows per second.
- Affordable big data- The first Terabyte of data processed each month is free.
On the other hand, Google Cloud Bigtable provides the following key features:
- Unmatched Performance: Single-digit millisecond latency and over 2X the performance per dollar of unmanaged NoSQL alternatives.
- Open Source Interface: Because Cloud Bigtable is accessed through the HBase API, it is natively integrated with much of the existing big data and Hadoop ecosystem and supports Google’s big data products. Additionally, data can be imported from or exported to existing HBase clusters through simple bulk ingestion tools using industry-standard formats.
- Low Cost: By providing a fully managed service and exceptional efficiency, Cloud Bigtable’s total cost of ownership is less than half the cost of its direct competition.
"High Performance" is the top reason why over 17 developers like Google BigQuery, while over 5 developers mention "High performance" as the leading cause for choosing Google Cloud Bigtable.
Sentry, Vine Labs, and Webedia are some of the popular companies that use Google BigQuery, whereas Google Cloud Bigtable is used by Spotify, Resultados Digitais, and Rainist. Google BigQuery has a broader approval, being mentioned in 156 company stacks & 39 developers stacks; compared to Google Cloud Bigtable, which is listed in 17 company stacks and 3 developer stacks.
I'm trying to build a way to read financial data really, really fast, for low cost. We are write/update-light (in this arena) and read-heavy. Google BigQuery being serverless can keep costs beyond low, but query speeds are always a few seconds because, I think, of the lack of indexing and potential to take advantage of the structure of the common queries. I have tried various partitions on BigQuery to speed things up too with some success but nothing extraordinary. I have never used Google Cloud Bigtable but get how it works conceptually. I believe it would make date-range based queries markedly faster. Question is, are there ways to take advantage of date-ranges in BigQuery, or does it makes sense to just shift to BigTable for mega-fast reads? I'd love to get sub-50ms.
As a DataWarehouse Solution Google Bigquery is meant more for Large Data Analysis then real time Write/Update. You can go with BigTable instead of BigQuery but be prepare for the hight cost. Also, in most of the Data solution if you are looking for heavy real time Wrire/Update you have to put some cost on the solution. For more detail you can check this link https://cloud.google.com/blog/products/gcp/in-memory-query-execution-in-google-bigquery
Cloud Data-warehouse is the centerpiece of modern Data platform. The choice of the most suitable solution is therefore fundamental.
Our benchmark was conducted over BigQuery and Snowflake. These solutions seem to match our goals but they have very different approaches.
BigQuery is notably the only 100% serverless cloud data-warehouse, which requires absolutely NO maintenance: no re-clustering, no compression, no index optimization, no storage management, no performance management. Snowflake requires to set up (paid) reclustering processes, to manage the performance allocated to each profile, etc. We can also mention Redshift, which we have eliminated because this technology requires even more ops operation.
BigQuery can therefore be set up with almost zero cost of human resources. Its on-demand pricing is particularly adapted to small workloads. 0 cost when the solution is not used, only pay for the query you're running. But quickly the use of slots (with monthly or per-minute commitment) will drastically reduce the cost of use. We've reduced by 10 the cost of our nightly batches by using flex slots.
Finally, a major advantage of BigQuery is its almost perfect integration with Google Cloud Platform services: Cloud functions, Dataflow, Data Studio, etc.
BigQuery is still evolving very quickly. The next milestone, BigQuery Omni, will allow to run queries over data stored in an external Cloud platform (Amazon S3 for example). It will be a major breakthrough in the history of cloud data-warehouses. Omni will compensate a weakness of BigQuery: transferring data in near real time from S3 to BQ is not easy today. It was even simpler to implement via Snowflake's Snowpipe solution.
We also plan to use the Machine Learning features built into BigQuery to accelerate our deployment of Data-Science-based projects. An opportunity only offered by the BigQuery solution
Pros of Google BigQuery
- High Performance28
- Easy to use25
- Fully managed service21
- Cheap Pricing19
- Process hundreds of GB in seconds16
- Full table scans in seconds, no indexes needed11
- Big Data11
- Always on, no per-hour costs8
- Good combination with fluentd6
- Machine learning4
Pros of Google Cloud Bigtable
- High performance11
- Fully managed9
- High scalability5
Sign up to add or upvote prosMake informed product decisions
Cons of Google BigQuery
- You can't unit test changes in BQ data1
Cons of Google Cloud Bigtable
Sign up to add or upvote consMake informed product decisions
What is Google BigQuery?
What is Google Cloud Bigtable?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Google BigQuery?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Google Cloud Bigtable?
Sign up to get full access to all the tool integrationsMake informed product decisions