Amazon Athena is an interactive query service that makes it easy to analyze data directly in Amazon S3 using standard SQL. With a few clicks in the AWS Management Console, customers can point Athena at their data stored in S3 and begin using standard SQL to run ad-hoc queries and get results in seconds. Athena is serverless, so there is no infrastructure to setup or manage, and customers pay only for the queries they run. You can use Athena to process logs, perform ad-hoc analysis, and run…
$5
per TB of Data Scanned
Amazon DynamoDB
Score 8.5 out of 10
N/A
Amazon DynamoDB is a cloud-native, NoSQL, serverless database service.
$0
capacity unit per hour
Pricing
Amazon Athena
Amazon DynamoDB
Editions & Modules
Price per Query
$5.00
per TB of Data Scanned
Provisioned - Read Operation
$0.00013
capacity unit per hour
Provisioned - Write Operation
$0.00065
capacity unit per hour
Provisioned - Global Tables
$0.000975
per Read Capacity
On-Demand Streams
$0.02
per 100,000 read operations
Provisioned - Streams
$0.02
per 100,000 read operations
On-Demand Data Requests Outside AWS Regions
$0.09
per GB
Provisioned - Data Requests Outside AWS Regions
$0.09
per GB
On-Demand Snapshot
$0.10
per GB per month
Provisioned - Snapshot
$0.10
per GB per month
On-Demand Restoring a Backup
$0.15
per GB
Provisioned - Restoring a Backup
$0.15
per GB
On-Demand Point-in-Time Recovery
$0.20
per GB per month
Provisioned - Point-in-Time Recovery
$0.20
per GB per month
On-Demand Read Operation
$0.25
per million requests
On-Demand Data Stored
$0.25
per GB per month
Provisioned - Data Stored
$0.25
per GB per month
On-Demand - Write Operation
$1.25
per million requests
On-Demand Global Tables
$1.875
per million write operations replicated
Offerings
Pricing Offerings
Amazon Athena
Amazon DynamoDB
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon Athena
Amazon DynamoDB
Features
Amazon Athena
Amazon DynamoDB
Database-as-a-Service
Comparison of Database-as-a-Service features of Product A and Product B
Amazon Athena
8.6
Ratings
1% below category average
Amazon DynamoDB
-
Ratings
Automatic software patching
8.20 Ratings
00 Ratings
Database scalability
9.00 Ratings
00 Ratings
Automated backups
7.70 Ratings
00 Ratings
Database security provisions
9.20 Ratings
00 Ratings
Monitoring and metrics
8.00 Ratings
00 Ratings
Automatic host deployment
9.20 Ratings
00 Ratings
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Best suited for analyzing huge amounts of data by just querying on Amazon Athena. Amazon Athena is also best to integrate with Amazon Quickight for visualization and reporting of data. Easy to work with CSV, JSON, and columnar data formats like Parquet, and ORC. Less appropriate to work with AVRO data format and also stored procedures are not supported in Amazon Athena. The size of a single row is also limited to 32 MB.
It is useful use-case by use-case. For our use case, it was the best and easiest option for the integration as well as development side. It is serverless so no need of deployment and maintenance hustle. It is easy to scale up due to the same functionality. Supports AWS Security features and just a click away for enabling it so security is good.
It's core to our business, we couldn't survive without it. We use it to drive everything from FTP logins to processing stories and delivering them to clients. It's reliable and easy to query from all of our pipeline services. Integration with things like AWS Lambda makes it easy to trigger events and run code whenever something changes in the database.
Functionally, DynamoDB has the features needed to use it. The interface is not as easy to use, which impacts its usability. Being familiar with AWS in general is helpful in understanding the interface, however it would be better if the interface more closely aligned with traditional tools for managing datastores.
While the actual performance of DynamoDB can vary based on workload and region, it is generally highly responsive and well-regarded for delivering low-latency access to data, making it a strong choice for applications with stringent performance requirements. Organizations often choose DynamoDB for its ability to provide a reliable and performant database service, particularly when combined with effective application design and optimization.
Amazon Athena, a product from Amazon, competes with offerings from Google and Microsoft. Overall, I think your database choice depends on some of the other applications you are running at your company. For example, if you are using Microsoft Power BI for reporting needs, you might want to consider going the Azure route.
For our use case, we needed a noSQL that would work with AWS Lambdas of specific parts of the internal web applications. We optimized billing and uses , diversified databases for various parts; so it’s not very expensive.
I have taken one point away due to its size limits. In case the application requires queries, it becomes really complicated to read and write data. When it comes to extremely large data sets such as the case in my company, a third-party logistics company, where huge amount of data is generated on a daily basis, even though the scalability is good, it becomes difficult to manage all the data due to limits.
It's easy to store and query data on S3. Multiple teams can query the same data to generate their reports. It removes the need for a full-fledged data warehouse for a startup. Saves costs.
Improved team efficiency on monitoring user activities by easy logging and reporting.
As the dataset gets heavier on S3, one needs to understand partitioning and that leads to the requirement of expertise.
Businesses may only pay for the services they actually use thanks to DynamoDB's usage-based pricing approach.
AWS handles hardware provisioning, data recovery, fault tolerance, patching, and database upgrades for DynamoDB since it is a fully managed database service.
DynamoDB differs from conventional relational databases in terms of its data model, which might be difficult for developers accustomed to dealing with SQL-based systems.