StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Big Data As A Service
  5. Amazon Athena vs Google BigQuery

Amazon Athena vs Google BigQuery

OverviewDecisionsComparisonAlternatives

Overview

Google BigQuery
Google BigQuery
Stacks1.8K
Followers1.5K
Votes152
Amazon Athena
Amazon Athena
Stacks519
Followers840
Votes49

Amazon Athena vs Google BigQuery: What are the differences?

Introduction:

Amazon Athena and Google BigQuery are both cloud-based data warehousing and analytics services. While they have similarities in terms of providing scalable and cost-effective solutions for processing large datasets, there are key differences between the two platforms. The following paragraphs highlight some of these differences:

  1. Data Storage and Structure: Amazon Athena stores data in Amazon S3, allowing users to directly query the data without the need for complex ETL processes. On the other hand, Google BigQuery has its own dedicated storage system, which eliminates the need for a separate storage service. It also supports a wide range of data formats, including native support for nested and repeated fields.

  2. Query Execution and Performance: Amazon Athena uses Presto, an open-source distributed SQL query engine, for query execution. This makes it suitable for running ad-hoc queries and provides flexibility in terms of data formats. Google BigQuery, on the other hand, uses a proprietary query engine optimized for large-scale data processing. It employs a columnar storage format and parallel processing techniques, which generally contribute to faster query performance.

  3. Pricing Structure: Amazon Athena follows a pay-per-query pricing model, where users are billed based on the amount of data scanned by the queries. This can provide cost savings for occasional or small-scale usage. In contrast, Google BigQuery has tiered pricing based on storage and query usage, which may be more suitable for users with predictable or high-volume workloads.

  4. Data Partitioning and Clustering: Amazon Athena supports partitioning and clustering of data, allowing users to optimize query performance by reducing the amount of data scanned. This is particularly useful for table scans on large datasets. Google BigQuery, on the other hand, automatically partitions and clusters data based on the table's schema and query patterns, further enhancing query performance.

  5. Integration with Ecosystem: Amazon Athena integrates well with other AWS services, making it a good choice for users already utilizing the AWS ecosystem. It also has seamless integration with AWS Glue, allowing for automated and scalable ETL processes. Google BigQuery integrates well with other Google Cloud Platform services, providing a cohesive experience for users in the Google Cloud ecosystem.

  6. Data Transfer and Loading: Amazon Athena supports querying data directly from external sources like Amazon Redshift and Amazon DynamoDB, making it easier to analyze data across different services. Google BigQuery, on the other hand, offers native connectors for various Google services like Google Sheets and Google Analytics, simplifying data loading and analysis within the Google Cloud environment.

In Summary, Amazon Athena and Google BigQuery differ in terms of data storage, query execution, pricing structure, data partitioning and clustering, ecosystem integration, and data transfer/loading capabilities. The choice between the two depends on specific use cases, existing infrastructure, and preferences.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Google BigQuery, Amazon Athena

Julien
Julien

CTO at Hawk

Sep 19, 2020

Decided

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

193k views193k
Comments
Pavithra
Pavithra

Mar 12, 2020

Needs adviceonAmazon S3Amazon S3Amazon AthenaAmazon AthenaAmazon RedshiftAmazon Redshift

Hi all,

Currently, we need to ingest the data from Amazon S3 to DB either Amazon Athena or Amazon Redshift. But the problem with the data is, it is in .PSV (pipe separated values) format and the size is also above 200 GB. The query performance of the timeout in Athena/Redshift is not up to the mark, too slow while compared to Google BigQuery. How would I optimize the performance and query result time? Can anyone please help me out?

522k views522k
Comments

Detailed Comparison

Google BigQuery
Google BigQuery
Amazon Athena
Amazon Athena

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.

Amazon Athena is an interactive query service that makes it easy to analyze data in Amazon S3 using standard SQL. Athena is serverless, so there is no infrastructure to manage, and you pay only for the queries that you run.

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.;The right interface- Separate interfaces for administration and developers will make sure that you have access to the tools you need.
-
Statistics
Stacks
1.8K
Stacks
519
Followers
1.5K
Followers
840
Votes
152
Votes
49
Pros & Cons
Pros
  • 28
    High Performance
  • 25
    Easy to use
  • 22
    Fully managed service
  • 19
    Cheap Pricing
  • 16
    Process hundreds of GB in seconds
Cons
  • 1
    You can't unit test changes in BQ data
  • 0
    Sdas
Pros
  • 16
    Use SQL to analyze CSV files
  • 8
    Glue crawlers gives easy Data catalogue
  • 7
    Cheap
  • 6
    Query all my data without running servers 24x7
  • 4
    No data base servers yay
Integrations
Xplenty
Xplenty
Fluentd
Fluentd
Looker
Looker
Chartio
Chartio
Treasure Data
Treasure Data
Amazon S3
Amazon S3
Presto
Presto

What are some alternatives to Google BigQuery, Amazon Athena?

Apache Spark

Apache Spark

Spark is a fast and general processing engine compatible with Hadoop data. It can run in Hadoop clusters through YARN or Spark's standalone mode, and it can process data in HDFS, HBase, Cassandra, Hive, and any Hadoop InputFormat. It is designed to perform both batch processing (similar to MapReduce) and new workloads like streaming, interactive queries, and machine learning.

Amazon Redshift

Amazon Redshift

It is optimized for data sets ranging from a few hundred gigabytes to a petabyte or more and costs less than $1,000 per terabyte per year, a tenth the cost of most traditional data warehousing solutions.

Qubole

Qubole

Qubole is a cloud based service that makes big data easy for analysts and data engineers.

Presto

Presto

Distributed SQL Query Engine for Big Data

Amazon EMR

Amazon EMR

It is used in a variety of applications, including log analysis, data warehousing, machine learning, financial analysis, scientific simulation, and bioinformatics.

Apache Flink

Apache Flink

Apache Flink is an open source system for fast and versatile data analytics in clusters. Flink supports batch and streaming analytics, in one system. Analytical programs can be written in concise and elegant APIs in Java and Scala.

lakeFS

lakeFS

It is an open-source data version control system for data lakes. It provides a “Git for data” platform enabling you to implement best practices from software engineering on your data lake, including branching and merging, CI/CD, and production-like dev/test environments.

Druid

Druid

Druid is a distributed, column-oriented, real-time analytics data store that is commonly used to power exploratory dashboards in multi-tenant environments. Druid excels as a data warehousing solution for fast aggregate queries on petabyte sized data sets. Druid supports a variety of flexible filters, exact calculations, approximate algorithms, and other useful calculations.

Altiscale

Altiscale

we run Apache Hadoop for you. We not only deploy Hadoop, we monitor, manage, fix, and update it for you. Then we take it a step further: We monitor your jobs, notify you when something’s wrong with them, and can help with tuning.

Snowflake

Snowflake

Snowflake eliminates the administration and management demands of traditional data warehouses and big data platforms. Snowflake is a true data warehouse as a service running on Amazon Web Services (AWS)—no infrastructure to manage and no knobs to turn.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase