Need advice about which tool to choose?Ask the StackShare community!
Google BigQuery vs Stitch: What are the differences?
What is 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..
What is Stitch? All your data. In your data warehouse. In minutes. Stitch is a simple, powerful ETL service built for software developers. Stitch evolved out of RJMetrics, a widely used business intelligence platform. When RJMetrics was acquired by Magento in 2016, Stitch was launched as its own company.
Google BigQuery and Stitch can be primarily classified as "Big Data as a Service" tools.
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, Stitch provides the following key features:
- Connect to your ecosystem of data sources - UI allows you to configure your data pipeline in a way that balances data freshness with cost and production database load
- Replication frequency - Choose full or incremental loads, and determine how often you want them to run - from every minute, to once every 24 hours
- Data selection - Configure exactly what data gets replicated by selecting the tables, fields, collections, and endpoints you want in your warehouse
"High Performance" is the primary reason why developers consider Google BigQuery over the competitors, whereas "3 minutes to set up" was stated as the key factor in picking Stitch.
According to the StackShare community, Google BigQuery has a broader approval, being mentioned in 160 company stacks & 41 developers stacks; compared to Stitch, which is listed in 22 company stacks and 4 developer stacks.
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 service22
- Cheap Pricing19
- Process hundreds of GB in seconds16
- Big Data12
- Full table scans in seconds, no indexes needed11
- Always on, no per-hour costs8
- Good combination with fluentd6
- Machine learning4
- Easy to manage1
- Easy to learn0
Pros of Stitch
- 3 minutes to set up8
- Super simple, great support4
Sign up to add or upvote prosMake informed product decisions
Cons of Google BigQuery
- You can't unit test changes in BQ data1
- Sdas0
Cons of Stitch
Sign up to add or upvote consMake informed product decisions
What is Google BigQuery?
What is Stitch?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Google BigQuery?
What companies use Stitch?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Stitch?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+16
+25
+47
+31
+39+26