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
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
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 April 2026, in the Cloud Data Warehouse category, the mindshare of AWS Lake Formation is 4.4%, down from 5.1% compared to the previous year. The mindshare of BigQuery is 7.7%, up from 6.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Data Warehouse Mindshare Distribution
ProductMindshare (%)
BigQuery7.7%
AWS Lake Formation4.4%
Other87.9%
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

"We use this to reduce latency from minutes to seconds, as we aim for real-time visibility into patient healthcare monitoring."
"AWS Lake Formation works hand in hand with other products."
"The LF-Tag system with granular permissions was key to the project as a functionality of AWS Lake Formation."
"The most important advantage of using AWS Lake Formation is its ability to connect the data lake to the other technologies in AWS."
"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."
"We use AWS Lake Formation typically for the data warehouse."
"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."
"A favorite feature of AWS Lake Formation is that it provides us with visibility into who has access to a particular table or database in Glue."
"BigQuery excels at data analysis. It processes vast amounts of information using its advanced architecture and sophisticated querying capabilities, making it crucial for critical insights and safe for handling sensitive data."
"The most valuable features of this solution, in my opinion, are speed and performance, as well as cost-effectiveness."
"BigQuery can be used for any type of company. It has the capability of building applications and storing data. It can be used for OLTP or OLAP. It has many other products within the Google space."
"The setup is simple."
"It is stable and reliable; there are no bugs or glitches."
"The most valuable aspect of BigQuery is its ability to handle high data workloads without causing friction with our online systems."
"The solution's reporting, dashboard, and out-of-the-box capabilities match exactly our requirements."
"The product's most valuable features include its scalability and the ability to handle complex queries on large datasets."
 

Cons

"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."
"AWS Lake Formation's pricing could be cheaper."
"The solution could make improvements around orchestration and doing some automation stuff on AWS front automation. It would be useful if we could use automation to build images and use hardened images which are CIS compliant."
"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."
"The solution could make improvements around orchestration and doing some automation stuff on AWS front automation."
"You need to have data experience to use the product."
"For the end-users, it's not as user-friendly as it could be."
"The primary hurdle in this migration lies in the initial phase of moving substantial volumes of data to cloud-based platforms."
"It can be slower and more problematic compared to other platforms such as Snowflake."
"I am unsure of the scalability because I need to test it with a bigger project."
"I understand that Snowflake has made some improvements on its end to further reduce costs, so I believe BigQuery can catch up."
"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."
"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. You have to actually open a ticket and then follow it up with Google support."
"So our challenge in Yemen is convincing many people to go to cloud services."
"An area for improvement in BigQuery is its UI because it's not working very well. Pricing for the solution is also very high."
 

Pricing and Cost Advice

"AWS Lake Formation is a bit expensive."
"The platform is inexpensive."
"The pricing appears to be competitive for the intended usage scenarios we have in mind."
"Price-wise, I think that is very reasonable."
"The pricing is good and there are no additional costs involved."
"The solution's pricing is cheaper compared to other solutions."
"The solution is pretty affordable and quite cheap in comparison to PDP or Cloudera."
"We are above the free threshold, so we are paying around 40 euros per month for BigQuery."
"The tool has competitive pricing."
report
Use our free recommendation engine to learn which Cloud Data Warehouse solutions are best for your needs.
889,855 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Manufacturing Company
8%
Retailer
7%
Government
6%
Financial Services Firm
16%
Manufacturing Company
12%
Computer Software Company
8%
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 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.
889,855 professionals have used our research since 2012.