No more typing reviews! Try our Samantha, our new voice AI agent.

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
9th
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
3rd
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 May 2026, in the Cloud Data Warehouse category, the mindshare of AWS Lake Formation is 4.1%, down from 5.3% compared to the previous year. The mindshare of BigQuery is 7.4%, up from 6.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Data Warehouse Mindshare Distribution
ProductMindshare (%)
BigQuery7.4%
AWS Lake Formation4.1%
Other88.5%
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 features and capabilities of AWS Lake Formation that I have found most valuable are that it is really convenient to see all the different data assets that were configured and understand who has and what type of service has or does not have access to those services."
"We use AWS Lake Formation typically for the data warehouse."
"The integration of AWS Lake Formation with the IAM for authentication and authorization is very good; I didn't have any problems in the setup and thought it was simple."
"The solution is quite good at handling analytics."
"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."
"We have observed measurable benefits in terms of cost savings, time savings, resource savings, and efficiency improvements in our workflows."
"The main benefits that I have seen from using AWS Lake Formation are related to FinOps because you have control of your data and can track your costs since AWS Lake Formation is integrated into a unique platform, which is AWS Cloud Service."
"To be frank, the performance, reliability, and everything else have improved, even the downtime."
"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."
"The solution's reporting, dashboard, and out-of-the-box capabilities match exactly our requirements."
"The main thing I like about BigQuery is storage. We did an on-premise BigQuery migration with trillions of records. Usually, we have to deal with insufficient storage on-premises, but in BigQuery, we don't get that because it's like cloud storage, and we can have any number of records. That is one advantage. The next major advantage is the column length. We have some limits on column length on-premises, like 10,000, and we have to design it based on that. However, with BigQuery, we don't need to design the column length at all. It will expand or shrink based on the records it's getting. I can give you a real-life example based on our migration from on-premises to GCP. There was a dimension table with a general number of records, and when we queried that on-premises, like in Apache Spark or Teradata, it took around half an hour to get those records. In BigQuery, it was instant. As it's very fast, you can get it in two or three minutes. That was very helpful for our engineers. Usually, we have to run a query on-premises and go for a break while waiting for that query to give us the results. It's not the case with BigQuery because it instantly provides results when we run it. So, that makes the work fast, it helps a lot, and it helps save a lot of time. It also has a reasonable performance rate and smart tuning. Suppose we need to perform some joins, BigQuery has a smart tuning option, and it'll tune itself and tell us the best way a query can be done in the backend. To be frank, the performance, reliability, and everything else have improved, even the downtime. Usually, on-premise servers have some downtime, but as BigQuery is multiregional, we have storage in three different locations. So, downtime is also not getting impacted. For example, if the Atlantic ocean location has some downtime, or the server is down, we can use data that is stored in Africa or somewhere else. We have three or four storage locations, and that's the main advantage."
"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."
"BigQuery is similar to Snowflake in the way it manages data analytics and completely decouples storage from compute, offering a 100% managed, infrastructure-free solution where you can build an end-to-end data platform directly from a browser console."
"The feature called calibrating the capacity is valuable."
"It is stable and reliable; there are no bugs or glitches."
 

Cons

"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."
"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."
"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."
"I think AWS Lake Formation could improve by enforcing the least privilege by design, moving from ad hoc grants to role-based access controls."
"Information about the pricing, cost, and setup cost of the AWS solutions would be beneficial."
"AWS Lake Formation's pricing could be cheaper."
"If I could improve AWS Lake Formation, I would add more integrations with SageMaker."
"The main challenge we faced with AWS Lake Formation was related to cross-account sharing. Granting access to other AWS accounts for tables or databases in a different AWS account was somewhat difficult."
"There is a good amount of documentation out there, but they're consistently making changes to the platform, and, like, their literature hasn't been updated on some plans."
"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."
"With other columnar databases like Snowflake, you can actually increase your VM size or increase your machine size, and you can buy more memory and it will start working faster, but that's not available in BigQuery."
"The product’s performance could be much faster."
"It would be helpful if they could provide some dashboards where you can easily view charts and information."
"BigQuery should integrate with other tools, such as Cloud Logging and Local Studio, to enhance its capabilities further and enable powerful and innovative analyses."
"When I open many of the Google Cloud products, I am in an environment that I do not feel familiar with; it is a little overwhelming."
"We'd like to have more integrations with other technologies."
 

Pricing and Cost Advice

"AWS Lake Formation is a bit expensive."
"The product operates on a pay-for-use model. Costs include storage and query execution, which can accumulate based on data volume and complexity."
"The pricing appears to be competitive for the intended usage scenarios we have in mind."
"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."
"BigQuery is inexpensive."
"The solution's pricing is cheaper compared to other solutions."
"We are above the free threshold, so we are paying around 40 euros per month for BigQuery."
"The pricing is good and there are no additional costs involved."
"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."
report
Use our free recommendation engine to learn which Cloud Data Warehouse solutions are best for your needs.
892,776 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Manufacturing Company
9%
Government
6%
Retailer
6%
Financial Services Firm
17%
Manufacturing Company
10%
Computer Software Company
8%
Media Company
8%
 

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 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?
With what I have seen in BigQuery, I had some response times problems, but then it is an analytical database and not a transactional database, so it comes with eventual consistency. I cannot have e...
What is your primary use case for BigQuery?
We are mostly dealing with Google solutions such as BigQuery, NoSQL, SQL analytical database, secrets manager, and most of the serverless infrastructure as well, databases. I run SQL queries on Big...
 

Also Known As

No data available
BQ
 

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: April 2026.
892,776 professionals have used our research since 2012.