Try our new research platform with insights from 80,000+ expert users

AWS Lake Formation vs BigQuery comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 18, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

AWS Lake Formation
Ranking in Cloud Data Warehouse
8th
Average Rating
8.0
Reviews Sentiment
5.7
Number of Reviews
21
Ranking in other categories
No ranking in other categories
BigQuery
Ranking in Cloud Data Warehouse
4th
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
43
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2026, in the Cloud Data Warehouse category, the mindshare of AWS Lake Formation is 4.7%, down from 5.0% compared to the previous year. The mindshare of BigQuery is 8.0%, up from 7.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Data Warehouse Mindshare Distribution
ProductMindshare (%)
BigQuery8.0%
AWS Lake Formation4.7%
Other87.3%
Cloud Data Warehouse
 

Featured Reviews

Ciro Baldim Guerra - PeerSpot reviewer
Sr Analytics Engineer at Itau Unibanco S.A.
Has improved data governance by enabling clear ownership and structured access across teams
In my company, Itaú, we don't utilize all AWS offerings due to rigorous security measures. We operate approximately six to eight months behind other available services. I'm uncertain if gaps exist because of this limitation, though the system functions effectively for us. AWS Lake Formation offers column-level access control for databases, but we haven't implemented this feature either because it hasn't been approved by our compliance, governance, or security areas. In our current setup, everyone from my business unit uses the same consumer account. When access is requested for a table, everyone using that business unit account receives access. This could present a security concern, though it benefits new team members who automatically receive all necessary access permissions. However, I struggle to identify specific improvements needed in AWS Lake Formation.
Luís Silva - PeerSpot reviewer
Chief Technical Lead at a consultancy with 201-500 employees
Handles large data sets efficiently and offers flexible data management capabilities
The features I find most valuable in this solution are the ability to run and handle large data sets in a very efficient way with multiple types of data, relational as SQL data. It is kind of difficult to explain, but structured data and the ability to handle large data sets are key features. The data integration capabilities in BigQuery were, in fact, an issue at the beginning. There are two types of integrations. As long as integration is within Google, it is pretty simple. When you start to try to connect external clients to that data, it becomes more complex. It is not related to BigQuery, it is related to Google security model, which is not easy to manage. I would not call it an integration issue of BigQuery, I would call it an integration issue of Google security model.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The solution is quite good at handling analytics. It's done a good job at helping us centralize them."
"AWS Lake Formation significantly improves the structure of the data mesh, making it superior to previous structures we used."
"I can easily move data from cold storage to regular storage."
"The LF-Tag system with granular permissions was key to the project as a functionality of AWS Lake Formation."
"In the shortest form, what I appreciated about AWS Lake Formation was that the schema definition and data cataloging were quite good."
"AWS Lake Formation has several valuable features that enhance data management, and one particularly beneficial aspect is how it facilitates better collaboration within data teams."
"AWS Lake Formation significantly improves the structure of the data mesh, making it superior to previous structures we used."
"The most important advantage in using AWS Lake Formation is its ability to connect the data lake to the other technologies in AWS. This is what I advise my clients."
"We basically used it to store server data and generate reports for enterprise architects. It was a valuable tool for our enterprise design architect."
"When integrating their system into the cloud-based solutions, we were able to increase their efficiency and overall productivity twice compared with their on-premises option."
"It has a proprietary way of storing and accessing data in its own data store and is 100% managed without you needing to install anything. There is no need to arrange for any infrastructure to be able to use this solution."
"Its integration with other tools like Atlan through a Google Chrome extension is highly beneficial."
"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."
"This solution is highly scalable."
"It's pretty stable. It's fast, and it is able to go through large quantities of data pretty quickly."
"The initial setup process is easy."
 

Cons

"Athena can be a bit clunky when writing queries, indicating a potential enhancement point for easier user interaction with query tools such as DataGrip using provided driver JARs."
"Lake Formation could enhance its capabilities in audit logs, real-time monitoring, and advanced data governance."
"AWS Lake Formation's pricing could be cheaper."
"I haven't seen any measurable benefits from using AWS Lake Formation, such as time saving, resource saving, or efficiency improvements."
"Rather than creating an additional hundred tools, optimizing a tool to have a centralized location to do governance would be beneficial."
"I would appreciate online support, which I don't have access to in my corporation at the bank, so that is important."
"For the end-users, it's not as user-friendly as it could be."
"In our experience what could be improved are not the support, performance or monitoring, but at a managerial level, the very expensive professional services of AWS. This could be an area of improvement for them. It's too expensive to acquire their support."
"I would like to see version-based implementation and a fallback arrangement for data stored in BigQuery storage. These are some features I'm interested in."
"We would like to be able to calibrate the solution to run on top of a raw file."
"We'd like to have more integrations with other technologies."
"There are some limitations in the query latency compared to what it was three years ago."
"An area for improvement in BigQuery is its UI because it's not working very well. Pricing for the solution is also very high."
"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."
"Instead of connecting directly to BigQuery, we connect to GCP, Cloud Run, and then to BigQuery, which is a long process."
"So our challenge in Yemen is convincing many people to go to cloud services."
 

Pricing and Cost Advice

"AWS Lake Formation is a bit expensive."
"The price could be better. Usually, you need to buy the license for a year. Whenever you want more, you can subscribe to it, and you can use it. Otherwise, you can terminate the license. You can use it daily or monthly, and we use it based on a project's requirements."
"I have tried my own setup using my Gmail ID, and I think it had a $300 limit for free for a new user. That's what Google is offering, and we can register and create a project."
"1 TB is free of cost monthly. If you use more than 1 TB a month, then you need to pay 5 dollars extra for each TB."
"One terabyte of data costs $20 to $22 per month for storage on BigQuery and $25 on Snowflake. Snowflake is costlier for one terabyte, but BigQuery charges based on how much data is inserted into the tables. BigQuery charges you based on the amount of data that you handle and not the time in which you handle it. This is why the pricing models are different and it becomes a key consideration in the decision of which platform to use."
"Price-wise, I think that is very reasonable."
"The solution is pretty affordable and quite cheap in comparison to PDP or Cloudera."
"The pricing appears to be competitive for the intended usage scenarios we have in mind."
"The tool has competitive pricing."
report
Use our free recommendation engine to learn which Cloud Data Warehouse solutions are best for your needs.
884,122 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Manufacturing Company
8%
Retailer
7%
Computer Software Company
6%
Financial Services Firm
15%
Manufacturing Company
14%
Computer Software Company
10%
Media Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise15
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise9
Large Enterprise20
 

Questions from the Community

What is your experience regarding pricing and costs for AWS Lake Formation?
I don't understand much about the pricing of AWS Lake Formation, but I know how to search for the cost of Glue jobs, and I use the calculator in Amazon. I use a tool to preview the cost based on th...
What needs improvement with AWS Lake Formation?
Regarding areas of AWS Lake Formation that could be improved or enhanced, I prefer not to answer, mainly because I do not believe that I would be the most valuable person to ask, as I have not used...
What is your primary use case for AWS Lake Formation?
My usual use cases for AWS Lake Formation involved securing and governing the data resources that we configured in AWS, but we did not use the analytics or machine learning capabilities specificall...
What do you like most about BigQuery?
The initial setup process is easy.
What is your experience regarding pricing and costs for BigQuery?
I believe the cost of BigQuery is competitive versus the alternatives in the market, but it can become expensive if the tool is not used properly. It is on a per-consumption basis, the billing, so ...
What needs improvement with BigQuery?
There are areas that could be improved with BigQuery, such as more bolt-on capabilities and the ability to use more bolt-ons for APIs. Having more of a library of connectors would be really benefic...
 

Overview

 

Sample Customers

bp, Cerner, Expedia, Finra, HESS, intuit, Kellog's, Philips, TIME, workday
Information Not Available
Find out what your peers are saying about AWS Lake Formation vs. BigQuery and other solutions. Updated: March 2026.
884,122 professionals have used our research since 2012.