3/1/2023 0 Comments Metabase athena![]() If you’re running the same query every hour or day to power a BI dashboard, and the structure of the underlying data stays consistent, Redshift might be the better choice – especially if you’re willing to invest in infrastructure to ensure consistent performance come hell or high water.Īthena, on the other hand, might be your go-to for an ad-hoc query – most queries will just work, even on semi-structured or unstructured data, and they will return results without extensive tuning. Redshift would be the better choice if you have data coming in from diverse sources and you would like to transform that data, enforce consistent schema and formats, and create a single source that feeds a large number of business intelligence and reporting tools across the organization (see the AWS Athena FAQ ). Redshift is the more natural choice for data warehouse reporting, Athena for ad-hoc queries against S3 storage. However, here are the key factors to consider when deciding between Redshift and Athena: 1. The caveat from above still applies – your mileage may vary, every organization and every architecture is different, and so on. ![]() Let’s go a little bit more in-depth with… 4 Questions to decide where to run your analytic workloads
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |