We performed a comparison between Apache Hadoop and BigQuery based on real PeerSpot user reviews.
Find out in this report how the two Cloud Data Warehouse solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."High throughput and low latency. We start with data mashing on Hive and finally use this for KPI visualization."
"Data ingestion: It has rapid speed, if Apache Accumulo is used."
"The scalability of Apache Hadoop is very good."
"Hadoop is designed to be scalable, so I don't think that it has limitations in regards to scalability."
"The most valuable features are the ability to process the machine data at a high speed, and to add structure to our data so that we can generate relevant analytics."
"The most valuable feature is the database."
"I liked that Apache Hadoop was powerful, had a lot of tools, and the fact that it was free and community-developed."
"Its integration is Hadoop's best feature because that allows us to support different tools in a big data platform."
"The interface is what I find particularly valuable."
"As a cloud solution, it's easy to set up."
"BigQuery excels at structuring data, performing predictions, and conducting insightful analyses and it leverages machine learning and artificial intelligence capabilities, powered by Google's Duarte AI."
"We like the machine learning features and the high-performance database engine."
"There are some performance features like partitioning, which you can do based on an integer, and it improves the performance a lot."
"The query tool is scalable and allows for petabytes of data."
"The product is serverless. We only need to write SQL queries to analyze the data. We need to pay based on the number of queries. The retrieval time is very less. Even if you write large queries, the tool is able to bring back data in a few seconds."
"One of the most significant advantages lies in the decoupling of storage and compute which allows to independently scale storage and compute resources, with the added benefit of extremely cost-effective storage akin to object storage solutions."
"It would be good to have more advanced analytics tools."
"It would be helpful to have more information on how to best apply this solution to smaller organizations, with less data, and grow the data lake."
"In certain cases, the configurations for dealing with data skewness do not make any sense."
"I mentioned it definitely, and this is probably the only feature we can improve a little bit because the terminal and coding screen on Hadoop is a little outdated, and it looks like the old C++ bio screen. If the UI and UX can be improved slightly, I believe it will go a long way toward increasing adoption and effectiveness."
"Hadoop's security could be better."
"I think more of the solution needs to be focused around the panel processing and retrieval of data."
"We would like to have more dynamics in merging this machine data with other internal data to make more meaning out of it."
"From the Apache perspective or the open-source community, they need to add more capabilities to make life easier from a configuration and deployment perspective."
"It would be beneficial to integrate additional tools, particularly from a business intelligence perspective."
"It would be better if BigQuery didn't have huge restrictions. For example, when we migrate from on-premises to on-premise, the data which handles all ebook characters can be handled on-premise. But in BigQuery, we have huge restrictions. If we have some symbols, like a hash or other special characters, it won't accept them. Not in all cases, but it won't accept a few special characters, and when we migrate, we get errors. We need to use Regexp or something similar to replace that with another character. This isn't expected from a high-range technology like BigQuery. It has to adapt all products. For instance, if we have a TV Showroom, the TV symbol will be there in the shop name. Teradata and Apache Spark accept this, but BigQuery won't. This is the primary concern that we had. In the next release, it would be better if the query on the external table also had cache. Right now, we are using a GCS bucket, and in the native table, we have cache. For example, if we query the same table, it won't cost because it will try to fetch the records from the cached result. But when we run queries on the external table a number of times, it won't be cached. That's a major drawback of BigQuery. Only the native table has the cache option, and the external table doesn't. If there is an option to have an external table for cache purposes, it'll be a significant advantage for our organization."
"An area for improvement in BigQuery is its UI because it's not working very well. Pricing for the solution is also very high."
"The solution should reduce its pricing."
"We'd like to see more local data residency."
"The product’s performance could be much faster."
"They could enhance the platform's user accessibility."
"The price could be better. Compared to competing solutions, BigQuery is expensive. It's only suitable for enterprise customers, not small and medium-sized businesses, as they cannot afford this kind of solution. In the next release, it would be better if they improved their AI bot. Although machine learning and artificial intelligence are doing wonders, there is still a lot of room to enhance them."
Apache Hadoop is ranked 5th in Data Warehouse with 32 reviews while BigQuery is ranked 5th in Cloud Data Warehouse with 31 reviews. Apache Hadoop is rated 7.8, while BigQuery is rated 8.2. The top reviewer of Apache Hadoop writes "A file system for data collection that contains needed information and files". On the other hand, the top reviewer of BigQuery writes "Expandable and easy to set up but needs more local data residency". Apache Hadoop is most compared with Azure Data Factory, Microsoft Azure Synapse Analytics, Oracle Exadata, Snowflake and VMware Tanzu Greenplum, whereas BigQuery is most compared with Snowflake, Teradata, Oracle Autonomous Data Warehouse, Vertica and AWS Lake Formation. See our Apache Hadoop vs. BigQuery report.
See our list of best Cloud Data Warehouse vendors.
We monitor all Cloud Data Warehouse reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
