Need advice about which tool to choose?Ask the StackShare community!
Amazon Athena vs Amazon Quicksight: What are the differences?
Amazon Athena and Amazon QuickSight are two powerful cloud-based services offered by Amazon Web Services (AWS) that cater to specific needs in data analytics and visualization. Both services have their unique features and functionalities, making them suitable for different use cases. Below are the key differences between Amazon Athena and Amazon QuickSight.
Data Processing Methodology: Amazon Athena is a serverless interactive query service that allows users to directly query data stored in Amazon S3 using standard SQL syntax. It does not require any infrastructure setup or management, as it operates on a pay-per-query model. On the other hand, Amazon QuickSight is a fast, cloud-powered business intelligence (BI) service that focuses on data visualization and reporting. It allows users to connect various data sources, create interactive dashboards, and share those dashboards with others.
Usability and User Interface: Amazon Athena primarily targets data analysts, data engineers, and developers who are comfortable with writing SQL queries. It provides an SQL interface via the AWS Management Console, AWS Command Line Interface (CLI), or any JDBC/ODBC connection. Amazon QuickSight, on the other hand, is designed for business users and non-technical users who need to quickly create visualizations and reports. It offers a drag-and-drop interface with various built-in visualization options.
Data Source Integration: Amazon Athena directly integrates with data stored in Amazon S3. It supports various file formats, including Parquet, CSV, JSON, and more. Users can create external tables to map the data stored in S3 for querying purposes. In contrast, Amazon QuickSight can connect to different data sources such as Amazon S3, Amazon Redshift, Amazon RDS, and other third-party databases. It provides options to import data or set up a live connection to these sources.
Data Transformation and Preprocessing: Amazon Athena is primarily focused on querying and extracting data without performing extensive data transformations or preprocessing. It can extract data from files, but users need to apply transformations outside of Athena before ingesting the data. Amazon QuickSight, on the other hand, offers various data transformation capabilities such as data cleansing, filtering, joining, and aggregating within the tool itself. It allows users to perform these transformations for creating meaningful visualizations and reports.
Collaboration and Sharing: Amazon Athena does not have built-in collaboration features or sharing capabilities. It is primarily a query service for individual users or teams who have access to the same account. In contrast, Amazon QuickSight provides collaboration features, allowing users to invite others to view or edit dashboards. It also offers options to share dashboards publicly or embed them in other applications.
Pricing Model: Amazon Athena pricing is solely based on the amount of data scanned by the queries and the amount of data stored in Amazon S3. Users only pay for the queries they run and the storage they utilize. Amazon QuickSight, on the other hand, follows a subscription-based pricing model. It offers different pricing tiers based on the number of users and the level of functionality required.
In summary, Amazon Athena is a serverless query service designed for querying and analyzing data stored in Amazon S3 using SQL. It is suitable for data analysts and engineers who are comfortable with SQL syntax. On the other hand, Amazon QuickSight is a cloud-powered BI service focused on data visualization and reporting. It is geared towards business users and provides a user-friendly interface for creating interactive dashboards and sharing them with others.
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?
you can use aws glue service to convert you pipe format data to parquet format , and thus you can achieve data compression . Now you should choose Redshift to copy your data as it is very huge. To manage your data, you should partition your data in S3 bucket and also divide your data across the redshift cluster
First of all you should make your choice upon Redshift or Athena based on your use case since they are two very diferent services - Redshift is an enterprise-grade MPP Data Warehouse while Athena is a SQL layer on top of S3 with limited performance. If performance is a key factor, users are going to execute unpredictable queries and direct and managing costs are not a problem I'd definitely go for Redshift. If performance is not so critical and queries will be predictable somewhat I'd go for Athena.
Once you select the technology you'll need to optimize your data in order to get the queries executed as fast as possible. In both cases you may need to adapt the data model to fit your queries better. In the case you go for Athena you'd also proabably need to change your file format to Parquet or Avro and review your partition strategy depending on your most frequent type of query. If you choose Redshift you'll need to ingest the data from your files into it and maybe carry out some tuning tasks for performance gain.
I'll recommend Redshift for now since it can address a wider range of use cases, but we could give you better advice if you described your use case in depth.
It depend of the nature of your data (structured or not?) and of course your queries (ad-hoc or predictible?). For example you can look at partitioning and columnar format to maximize MPP capabilities for both Athena and Redshift
you can change your PSV fomat data to parquet file format with AWS GLUE and then your query performance will be improved
Pros of Amazon Athena
- Use SQL to analyze CSV files16
- Glue crawlers gives easy Data catalogue8
- Cheap7
- Query all my data without running servers 24x76
- No data base servers yay4
- Easy integration with QuickSight3
- Query and analyse CSV,parquet,json files in sql2
- Also glue and athena use same data catalog2
- No configuration required1
- Ad hoc checks on data made easy0
Pros of Amazon Quicksight
- Dataset versionning1
- Good integration with aws Glue ETL services1
- More features (table calculations, functions, insights)1
- Better integration with aws1
- Super cheap1
Sign up to add or upvote prosMake informed product decisions
Cons of Amazon Athena
Cons of Amazon Quicksight
- Very basic BI tool1
- Only works in AWS environments (not GCP, Azure)1