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
Azure Data Lake Storage
Score 8.2 out of 10
N/A
Azure Data Lake Storage Gen2 is a highly scalable and cost-effective data lake solution for big data analytics. It combines the power of a high-performance file system with massive scale and economy to help you speed your time to insight. Data Lake Storage Gen2 extends Azure Blob Storage capabilities and is optimized for analytics workloads.
N/A
Google BigQuery
Score 8.7 out of 10
N/A
Google's BigQuery is part of the Google Cloud Platform, a database-as-a-service (DBaaS) supporting the querying and rapid analysis of enterprise data.
Amazon redshift and EMR require explicit configuration for underlying compute infrastructure. In Amazon Athena, Users don't have to set up any underlying infrastructure. It saves a lot of costs required for infrastructure. Users have to pay only for scanned data. Athena is good …
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 …
We have used both Hadoop and GCS buckets for our storage needs of very large healthcare data. In terms of comparison with the Hadoop distributed Files system, Azure Data Lake Storage always stands in a far better position due to easy integration with various latest and widely …
Azure Data Lake Storage from a functionality perspective is a much easier solution to work with. It's implementation from Amazon EMR went smooth, and continued usage is definitely better. However, Amazon EMR was significantly cheaper overall between the high transaction fees …
We chose Azure Data Lake due to the fact that it was already a product under the Azure application suite. We didn't have to focus on integrating another 3rd party application within our environment. Also due to the fact Azure Data Lake scales its storage pools very efficiently, …
We decided long ago to develop for the Azure platform, so we only evaluate products from within Azure. And Azure Data Lake Storage is really the dominant offering within its space. But to give you a comparison, previously we used to use Azure SQL Database for our analytical …
Microsoft solutions provide great harmony in end-to-end data value creation, and Azure Data Lake Storage is highly compatible with other analytical solutions, e.g., Azure Data Factory and Databricks. So I would say that it is at the heart of the analytical solution in the …
AWS charges you on an hourly basis but Azure has a pricing model of per minute charge. In terms of short term subscriptions, Azure has more flexibility but it is more expensive. Azure has a much better hybrid cloud support in comparison with AWS. AWS provides direct connections …
I am much more familiar with Snowflake. I thought it was fairly straightforward to use and did not have to learn much syntax. With Azure Data Lake Storage, I have had to learn some new syntax and thought there was a steeper learning curve. We selected it because of cost savings.
We looked at the Amazon solution and it did not play as well with our existing tools and added a layer of maintenance that we were not willing to take on at the time. We thought that our Microsoft contract and support were good and that our internal team had the knowledge to …
The Azure Data Lake solution is designed for organizations that want to take advantage of big data. It provides a data platform that can help developers, data scientists, and analysts store data of any size and format and perform all types of processing and analytics across …
Fully serverless. We don’t manage clusters or warehouses. Requires us to manage virtual warehouses. BigQuery is cheaper for exploratory heavy queries; Snowflake is more predictable for sustained workloads. BigQuery is unbeatable if you’re deep in Google’s ecosystem; Snowflake …
Google BigQuery of course collects a much much larger array of raw data and can handle (practically) an unlimited amount of data. For a large enterprise like ours that relies on large-scale analytics, this is absolutely imperative. Google BigQuery can also combine GA4 data with …
Compared to PostgreSQL and MySQL, Google BigQuery is faster and more scalable for large datasets. It’s serverless, so there’s no need to manage infrastructure. We chose Google BigQuery for its ease of use built-in analytics features
The architecture of ETL was influenced by Data processing component which is Dataproc and there was a need for easy Query console with Access control capabilities with lesser overhead in managing the permission. This made the decision to move with Google BigQuery compare to …
is much better as it’s easily accessible provides velvet documentation and fulfils all our needs as well as easily integrated into clients, environment
Google BigQuery is simpler and I say it has simpler UI too. If you have a clear long term ask , mainly business intelligence needs then Google BigQuery offers you good. If you need too much of features under a single cloud and you are ok to be lil clumsy then you can check …
I have used most of the data analytics platforms. Based on my work, I have found that the user interface of Google BigQuery is simple to navigate. I like the front view - ease of joining tables, and integration with other platforms.
Compared to every other analytics DB solution I've used, Google BigQuery was by far the easiest to set up and maintain, and scale. The price was also much lower for our use case (internal data analysis).
For our usage, Google BigQuery is cheaper and more performant. The others have their place, but in certain scenarios, Google BigQuery is a better solution.
We actually use Snowflake and BigQuery in tandem because they both currently meet various needs. Redshift, however, has barely been used since our migration away from it. In the case of both Snowflake and BigQuery, they beat Redshift by a long shot. The main reasons are their …
PowerBI can connect to GA4 for example but the data processing is more complicated and it takes longer to create dashboards. Azure is great once the data import has been configured but it's not an easy task for small businesses as it is with BigQuery.
I came to use BigQuery from a traditional system like MS SQL server, the features which are available in BigQuery as a cloud service far outweigh the features from SQL server. I have not used other similar tools like Amazon Redshift but Google BigQuery serves multiple use cases …
Google BigQuery is cheaper and much faster as compared to both. While as compared to Snowflake , we tested it was faster and cheaper by 30%, that is after Snowflake tweaked their environment, if not for that it would have been 90% cheaper than snowflake. Redshift is not easy …
In my opinion, Google BigQuery is custom made to be the best data lake system that is easy to use, scalas to fit any business size, has inbuilt security, as well as tools for data integrity. Although a few other tools have some of the same functionality, Google BigQuery is the …
It's easier to connect data between BigQuery and looker studio instead of connecting the data between BigQuery and tableau in terms of data explore or dashboard creating. Therefore we are considering migrating dashboards from tableau to looker studio for the whole company. On …
When comparing Google BigQuery and Databricks, both platforms are powerful tools for managing and analyzing large datasets. BQ is ideal for businesses requiring large-scale analytics, reporting, and dashboarding with minimal operational overhead. It’s also great for ad-hoc …
Google BigQuery's main advantage over its direct competitors (Amazon Redshift and Azure Synapse) is that it is widely supported by non-Google software, while the others rely heavily on their own cloud ecosystems.
I have used other data manipulation tools like SQL Server and Google BigQuery feels more intuitive, Google provides so much documentation and tutorials that getting to know the software is not only easy but even satisfactory, so I'd say Google BigQuery is very superior to that …
Main reason is how it integrates directly with the google ecosystem which really facilitates the automatization proceses for the whole company. This ensures that sales and all the other departments have the correct information on a daily bases with a ease of use with day to day …
Amazon Redshift was a likely alternative we were considering , but it needs to be provisioned on cluster and nodes, which increases infrastructure management, whereas Google BigQuery is serverless, so no infra management :) Also, I remember when comparing them we did found out …
Google BigQuery as a platform allows for more integrations and customizability than many other offerings. Users mostly need to understand the basics of database and SQL programming in order to get the most from the product. However, other products like Hevo do have less of a …
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.
Azure Data Lake storage is well suited for applications/use cases within organizations where capturing and storing large amounts of data in any format is required, primarily for storing and processing purposes. It's an easy and cost-effective cloud solution for your application data. The ability to integrate with other Azure Services like Azure Databricks and Azure Data Factory is superb.
Google BigQuery is great for being the central datastore and entry point of data if you're on GCP. It seamlessly integrates with other Google products, meaning you can ingest data from other Google products with ease and little technical knowledge, and all of it is near real-time. Being serverless, BigQuery will scale with you, which means you don't have to worry about contention or spikes in demand/storage. This can, however, mean your costs can run away quickly or mount up at short notice.
Azure Data Lake Storage is extremely scalable. It allows us to scale up or down endlessly based on what we need including replication.
In terms of security, Azure Data Lake Storage fits our requirements really well as we can monitor and encrypt seamlessly. We can also assign permissions through roles and grant network-level access.
Due to the fact that it can scale, we are able to monitor the cost of storage and any given time and make financial decisions about our infrastructure based on how small or big we want to scale.
Its serverless architecture and underlying Dremel technology are incredibly fast even on complex datasets. I can get answers to my questions almost instantly, without waiting hours for traditional data warehouses to churn through the data.
Previously, our data was scattered across various databases and spreadsheets and getting a holistic view was pretty difficult. Google BigQuery acts as a central repository and consolidates everything in one place to join data sets and find hidden patterns.
Running reports on our old systems used to take forever. Google BigQuery's crazy fast query speed lets us get insights from massive datasets in seconds.
I'd like to see a better cross-platform native client. Azure Data Explorer is fine, but it's far from the "SSMS" kind of experience SQL Server users are used to.
Listing a large number of file is somewhat problematic and slow. Using the native C# library, running directly on an Azure VM, it can take several hours to list just a couple million files.
Switching from V1 to V2 requires the creation of a new Storage Account and that's pretty inconvenient.
It is challenging to predict costs due to BigQuery's pay-per-query pricing model. User-friendly cost estimation tools, along with improved budget alerting features, could help users better manage and predict expenses.
The BigQuery interface is less intuitive. A more user-friendly interface, enhanced documentation, and built-in tutorial systems could make BigQuery more accessible to a broader audience.
We have to use this product as its a 3rd party supplier choice to utilise this product for their data side backend so will not be likely we will move away from this product in the future unless the 3rd party supplier decides to change data vendors.
web UI is easy and convenient. Many RDBMS clients such as aqua data studio, Dbeaver data grid, and others connect. Range of well-documented APIs available. The range of features keeps expanding, increasing similar features to traditional RDBMS such as Oracle and DB2
I have never had any significant issues with Google Big Query. It always seems to be up and running properly when I need it. I cannot recall any times where I received any kind of application errors or unplanned outages. If there were any they were resolved quickly by my IT team so I didn't notice them.
I think Google Big Query's performance is in the acceptable range. Sometimes larger datasets are somewhat sluggish to load but for most of our applications it performs at a reasonable speed. We do have some reports that include a lot of complex calculations and others that run on granular store level data that so sometimes take a bit longer to load which can be frustrating.
BigQuery can be difficult to support because it is so solid as a product. Many of the issues you will see are related to your own data sets, however you may see issues importing data and managing jobs. If this occurs, it can be a challenge to get to speak to the correct person who can help you.
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.
The Azure Data Lake solution is designed for organizations that want to take advantage of big data. It provides a data platform that can help developers, data scientists, and analysts store data of any size and format and perform all types of processing and analytics across multiple platforms and programming languages. It can work with your existing solutions, such as identity management and security solutions. It also integrates with other data warehouses and cloud environments. It can be useful for organizations that need the above softwares.
Google BigQuery of course collects a much much larger array of raw data and can handle (practically) an unlimited amount of data. For a large enterprise like ours that relies on large-scale analytics, this is absolutely imperative. Google BigQuery can also combine GA4 data with external sources (like CRM tools), so our analytics can be unified. Due to our heavy reliance on GA4, Google BigQuery is the natural choice since it is a Google product and has better integration.
We have continued to expand out use of Google Big Query over the years. I'd say its flexibility and scalability is actually quite good. It also integrates well with other tools like Tableau and Power BI. It has served the needs of multiple data sources across multiple departments within my company.
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.
The cost can be high for more advanced work. In some cases, for instance, time limits and lab runtimes may be too short if you are too slow to learn what is explained as you go along.
promote flexible team communication. You can create different spaces for different teams, and share files and tasks.
In some places, Google BigQuery has helped us save some money by avoiding the need for expensive infrastructure and reducing some of the operational costs.
Scalability is up-to-date and really helpful in multiple places.
Knowledge transfer is easy as it is very user-friendly, so the learning curve has been reduced.
Also, it gives us more insights from our data, helping us make smarter decisions for our business.