Book Image

Serverless Analytics with Amazon Athena

By : Anthony Virtuoso, Mert Turkay Hocanin, Aaron Wishnick
Book Image

Serverless Analytics with Amazon Athena

By: Anthony Virtuoso, Mert Turkay Hocanin, Aaron Wishnick

Overview of this book

Amazon Athena is an interactive query service that makes it easy to analyze data in Amazon S3 using SQL, without needing to manage any infrastructure. This book begins with an overview of the serverless analytics experience offered by Athena and teaches you how to build and tune an S3 Data Lake using Athena, including how to structure your tables using open-source file formats like Parquet. You’ll learn how to build, secure, and connect to a data lake with Athena and Lake Formation. Next, you’ll cover key tasks such as ad hoc data analysis, working with ETL pipelines, monitoring and alerting KPI breaches using CloudWatch Metrics, running customizable connectors with AWS Lambda, and more. Moving on, you’ll work through easy integrations, troubleshooting and tuning common Athena issues, and the most common reasons for query failure. You will also review tips to help diagnose and correct failing queries in your pursuit of operational excellence. Finally, you’ll explore advanced concepts such as Athena Query Federation and Athena ML to generate powerful insights without needing to touch a single server. By the end of this book, you’ll be able to build and use a data lake with Amazon Athena to add data-driven features to your app and perform the kind of ad hoc data analysis that often precedes many of today’s ML modeling exercises.
Table of Contents (20 chapters)
1
Section 1: Fundamentals Of Amazon Athena
5
Section 2: Building and Connecting to Your Data Lake
9
Section 3: Using Amazon Athena
14
Chapter 11: Operational Excellence – Monitoring, Optimization, and Troubleshooting
15
Section 4: Advanced Topics

What is Query Federation?

Simply put, Query Federation refers to the concept that a query engine such as Athena may enlist the help of multiple datastores, working together, to execute your query. These datastores are usually capable of more than file-level CRUD operations. Most will support row-level scan, filter, and project operations, with some handling full SQL. We've mentioned this concept earlier in this book, typically concerning ETL versus querying in place. Let's take a closer look at the practical difference between a federated query and what we'll call a classic query.

The following diagram shows an example of a tried and true S3 data lake. There are multiple datastores, namely DynamoDB, RDS Aurora, and a generic database, all feeding into S3. Then, Athena, or another query engine, with the aid of Glue Data Catalog, can access all our data. This is a classic query. You submitted the query to Athena, and Athena directly answered your query by reading the...