Amazon DynamoDB vs. Google BigQuery

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Amazon DynamoDB
Score 8.5 out of 10
N/A
Amazon DynamoDB is a cloud-native, NoSQL, serverless database service.
$0
capacity unit per hour
Google BigQuery
Score 8.4 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.
$0.04
Pricing
Amazon DynamoDBGoogle BigQuery
Editions & Modules
Provisioned - Read Operation
$0.00013
capacity unit per hour
Provisioned - Write Operation
$0.00065
capacity unit per hour
Provisioned - Global Tables
$0.000975
per Read Capacity
On-Demand Streams
$0.02
per 100,000 read operations
Provisioned - Streams
$0.02
per 100,000 read operations
On-Demand Data Requests Outside AWS Regions
$0.09
per GB
Provisioned - Data Requests Outside AWS Regions
$0.09
per GB
On-Demand Snapshot
$0.10
per GB per month
Provisioned - Snapshot
$0.10
per GB per month
On-Demand Restoring a Backup
$0.15
per GB
Provisioned - Restoring a Backup
$0.15
per GB
On-Demand Point-in-Time Recovery
$0.20
per GB per month
Provisioned - Point-in-Time Recovery
$0.20
per GB per month
On-Demand Read Operation
$0.25
per million requests
On-Demand Data Stored
$0.25
per GB per month
Provisioned - Data Stored
$0.25
per GB per month
On-Demand - Write Operation
$1.25
per million requests
On-Demand Global Tables
$1.875
per million write operations replicated
Standard edition
$0.04 / slot hour
Enterprise edition
$0.06 / slot hour
Enterprise Plus edition
$0.10 / slot hour
Offerings
Pricing Offerings
Amazon DynamoDBGoogle BigQuery
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Amazon DynamoDBGoogle BigQuery
Considered Both Products
Amazon DynamoDB
Chose Amazon DynamoDB
For our use case, we needed a noSQL that would work with AWS Lambdas of specific parts of the internal web applications. We optimized billing and uses , diversified databases for various parts; so it’s not very expensive.
Chose Amazon DynamoDB
i think both depends on usuability and app requirement
Chose Amazon DynamoDB
Other all SQL Databases are based on the traditional Schema Structure and Amazon DynamoDB is NoSQL so you don't need to generate the SQL Schemas. You can store the data whatever you want, whenever you want. You can store data in structured or non-structured any way you want. If …
Chose Amazon DynamoDB
Both are Nosql db but when it comes to scalability i think, MongoDB is no where close to Amazon DynamoDB
Chose Amazon DynamoDB
Performance at high scales is better and the cost at high scales is less. If one has a ton of data generated and has to work their way through it, I think Amazon DynamoDB should the go-to database. There are no compromises when it comes to performance at a huge scale. With any …
Chose Amazon DynamoDB
MongoDB was basically the first approach we used but because there was concern that some data may miss we were reluctant to use it. Oracle Database and SQL Server was our second approach but it was throttling so in last we tested out Amazon DynamoDB and it met our requirement.
Chose Amazon DynamoDB
The Amazon Web Services managed Amazon DynamoDB has excellent features which makes it stand out from all the others in market right now. The management ease it offers is far superior than its competitors and on top of that the on-demand pricing model is an advantage which works …
Chose Amazon DynamoDB
MongoDB has some performance issues and can get corrupted from time to time and has needed to be rebuilt. We have not had that experience while using DynamoDB.
Chose Amazon DynamoDB
Compare to other products its so easier to set up, meeting all of our business requirements and easy usable, highly efficient and scalable.
Chose Amazon DynamoDB
high scalability #single-digit latency. #so much flexile. #very easy to use. # low maintenance.#GLobal Access
Chose Amazon DynamoDB
Amazon DynamoDB seems to be more cost effective and easy to integrate with other aws services.
Chose Amazon DynamoDB
Amazon DynamoDB supports larger throughput, with better SLA, also, we are considering unstructured data, so Amazon DynamoDB has become the final decision
Chose Amazon DynamoDB
The only thing that can be compared to DynamoDB from the selected services can be Aurora. It is just that we use Aurora for High-Performance requirements as it can be 6 times faster than normal RDS DB. Both of them have served as well in the required scenario and we are very …
Chose Amazon DynamoDB
Haven't had a chance to use this up to an extent to be compared to DynamoDB.
Chose Amazon DynamoDB
DynamoDB offers strong consistency, more fine-grained control over read and write capacities, and integrates seamlessly with other AWS services.
DynamoDB is designed for horizontal scalability and high throughput, making it a better choice for applications with rapidly changing …
Chose Amazon DynamoDB
AWS handles hardware provisioning, data recovery, fault tolerance, patching, and database upgrades for DynamoDB since it is a fully managed database service. Businesses can then concentrate on other aspects of their operations, including product development or customer service, …
Chose Amazon DynamoDB
The automation is much more subtle and it performs way better for internet-scale applications. No matter the number of connections, the performance doesn't dip even a bit.
Chose Amazon DynamoDB
cosmos user interface is not that much good in comparision with dynamodb also the response time compares with dynamodb is high.
Chose Amazon DynamoDB
DynamoDB's scalability is more automated and effortless, making it easier to handle rapid growth. Other tools require more manual configuration while DynamoDB simplifies database administration. Also, DynamoDB provides strong consistency while other tools like MongoDB and …
Chose Amazon DynamoDB
We are always assembling our solutions on AWS and DynamoDB is a better fit for us because of its simplicity.
DynamoDB has its ow sets of triggers that make this an integrated solution on AWS.
Besides, we wanted to use a key-value solution for our simple edge DB, and we didn't …
Chose Amazon DynamoDB
DynamoDB is slightly different than both the above-stated DBs, with RDS being a relational database and Redshift being a data warehouse used for heavier jobs and analytics and vast data. DynamoDB lies in between both, with it being a no SQL base that can relatively store …
Chose Amazon DynamoDB
Lesser flexibility but better performance, and more predictable development support are the key points where Amazon DynamoDB comes out on top, when compared to MongoDB.
Chose Amazon DynamoDB
Mongo services are outside of our Vpc and are on a different network. Since most of our infra is on AWS, dynamo by AWS was a natural choice. Most of our engineers are familiar with AWS sdk and the console so that brought in a much smaller learning curve for our engineering team
Chose Amazon DynamoDB
These other products don't offer the flexible database features that DynamoDB has.
Google BigQuery
Chose Google BigQuery
is much better as it’s easily accessible provides velvet documentation and fulfils all our needs as well as easily integrated into clients, environment
Chose Google BigQuery
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 …
Chose Google BigQuery
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.
Chose Google BigQuery
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).
Chose Google BigQuery
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.
Chose Google BigQuery
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 …
Chose Google 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 …
Chose Google BigQuery
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 …
Chose Google BigQuery
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 …
Chose Google BigQuery
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 …
Chose Google BigQuery
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 …
Chose Google BigQuery
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.
Chose Google BigQuery
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 …
Chose Google BigQuery
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 …
Chose Google BigQuery
Its same as compared to Big query. We go with big query because of clients requirements in project.
Chose Google BigQuery
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 …
Chose Google BigQuery
There are some areas in which this product is better while there are some in which others do better. It's not like Google BigQuery surpasses them in every metric. For a holistic view, I will say we use this because of - scalability, performance, ease of use, and seamless …
Chose Google BigQuery
The data performance of Google BigQuery is best as per other software. Limitations on Google BigQuery's data size are superior to those of Microsoft SQL. Obtaining real-time data from several IoT devices is another benefit.
Chose Google BigQuery
I personally find it by far simpler than Amazon redshift due it's onboarding seamlessness. For a quick start and simplify tye access to read the data big query provide better user experience and a smoother user interface. More importantly, the fact that Big Query can be easily …
Chose Google BigQuery
Compared to SingleStore, BigQuery has a big advantage of being completely serverless, and without practical limitations.

Compared to RedShift, we found the cost model to be more fitted to our needs.
Chose Google BigQuery
BigQuery can automatically scale to accommodate the data and query load, providing potentially unlimited scalability. At the same time, Redshift requires manual scaling efforts to increase or decrease capacity, which might affect performance during scaling operations.
Chose Google BigQuery
We focused more on data volume and less on full application capabilities. All in all, we found that the two solutions complement each other. For integration, some sources were better handled in SAP HANA, particularly other SAP systems where Google Big Query was more suitable …
Chose Google BigQuery
SingleStore has a much lower query latency compared to BigQuery. Thus, we segregate faster tasks to SingleStore, and use BigQuery has our main database to store all historical data.
Chose Google BigQuery
Google BigQuery i would say is better to use than AWS Redshift but not SQL products but this could be due to being more experience in Microsoft and AWS products. It would be really nice if it could use standard SQL server coding rather than having to learn another dialect of …
Chose Google BigQuery
First and foremost, Google BigQuery's pricing structure, based on data processing and storage, is more cost-effective for our needs. Secondly, since we already use other Google Cloud services, its tight integration with them especially, with Cloud Storage and Dataflow was a big …
Features
Amazon DynamoDBGoogle BigQuery
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Amazon DynamoDB
9.2
Ratings
4% above category average
Google BigQuery
-
Ratings
Performance9.30 Ratings00 Ratings
Availability9.50 Ratings00 Ratings
Concurrency9.00 Ratings00 Ratings
Security9.20 Ratings00 Ratings
Scalability9.40 Ratings00 Ratings
Data model flexibility8.20 Ratings00 Ratings
Deployment model flexibility10.00 Ratings00 Ratings
Database-as-a-Service
Comparison of Database-as-a-Service features of Product A and Product B
Amazon DynamoDB
-
Ratings
Google BigQuery
8.4
Ratings
3% below category average
Automatic software patching00 Ratings8.00 Ratings
Database scalability00 Ratings9.20 Ratings
Automated backups00 Ratings8.50 Ratings
Database security provisions00 Ratings8.60 Ratings
Monitoring and metrics00 Ratings8.00 Ratings
Automatic host deployment00 Ratings8.00 Ratings
Best Alternatives
Amazon DynamoDBGoogle BigQuery
Small Businesses
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Medium-sized Companies
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Enterprises
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Amazon DynamoDBGoogle BigQuery
Likelihood to Recommend
8.9
(0 ratings)
8.6
(0 ratings)
Likelihood to Renew
10.0
(0 ratings)
8.1
(0 ratings)
Usability
9.1
(0 ratings)
7.7
(0 ratings)
Performance
9.1
(0 ratings)
-
(0 ratings)
Support Rating
5.2
(0 ratings)
7.3
(0 ratings)
Product Scalability
9.1
(0 ratings)
-
(0 ratings)
User Testimonials
Amazon DynamoDBGoogle BigQuery
Likelihood to Recommend
It is useful use-case by use-case. For our use case, it was the best and easiest option for the integration as well as development side. It is serverless so no need of deployment and maintenance hustle. It is easy to scale up due to the same functionality. Supports AWS Security features and just a click away for enabling it so security is good.
Read full review
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.
Read full review
Pros
  • It's very easy to get started, creating a table with a partition/sort key and you're on your way.
  • You can scale up and down your read/write IO as needed.
  • You can store structured and unstructured data.
  • It works great with Web Development as it's JSON based.
Read full review
  • 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.
Read full review
Cons
  • Cost model may not be easy to control and may lead to higher costs if not carefully planned
  • Indexing may be a cost culprit when not planned, because it's not included on the data costs
  • The Query Language may not fulfill everybody's expectations, as it has less features than those of competitors.
Read full review
  • 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.
Read full review
Likelihood to Renew
It's core to our business, we couldn't survive without it. We use it to drive everything from FTP logins to processing stories and delivering them to clients. It's reliable and easy to query from all of our pipeline services. Integration with things like AWS Lambda makes it easy to trigger events and run code whenever something changes in the database.
Read full review
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.
Read full review
Usability
Functionally, DynamoDB has the features needed to use it. The interface is not as easy to use, which impacts its usability. Being familiar with AWS in general is helpful in understanding the interface, however it would be better if the interface more closely aligned with traditional tools for managing datastores.
Read full review
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
Read full review
Reliability and Availability
No answers on this topic
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.
Read full review
Performance
While the actual performance of DynamoDB can vary based on workload and region, it is generally highly responsive and well-regarded for delivering low-latency access to data, making it a strong choice for applications with stringent performance requirements. Organizations often choose DynamoDB for its ability to provide a reliable and performant database service, particularly when combined with effective application design and optimization.
Read full review
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.
Read full review
Support Rating
I have not had to contact support for this service, however I have had to contact AWS for other services and their support has been good.
Read full review
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.
Read full review
Alternatives Considered
For our use case, we needed a noSQL that would work with AWS Lambdas of specific parts of the internal web applications. We optimized billing and uses , diversified databases for various parts; so it’s not very expensive.
Read full review
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.
Read full review
Scalability
I have taken one point away due to its size limits. In case the application requires queries, it becomes really complicated to read and write data. When it comes to extremely large data sets such as the case in my company, a third-party logistics company, where huge amount of data is generated on a daily basis, even though the scalability is good, it becomes difficult to manage all the data due to limits.
Read full review
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.
Read full review
Return on Investment
  • Businesses may only pay for the services they actually use thanks to DynamoDB's usage-based pricing approach.
  • AWS handles hardware provisioning, data recovery, fault tolerance, patching, and database upgrades for DynamoDB since it is a fully managed database service.
  • DynamoDB differs from conventional relational databases in terms of its data model, which might be difficult for developers accustomed to dealing with SQL-based systems.
Read full review
  • 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.
Read full review
ScreenShots

Amazon DynamoDB Screenshots

Screenshot of Amazon DynamoDB in the AWS Console

Google BigQuery Screenshots

Screenshot of Migrating data warehouses to BigQuery - Features a streamlined migration path from Netezza, Oracle, Redshift, Teradata, or Snowflake to BigQuery using the fully managed BigQuery Migration Service.Screenshot of bringing any data into BigQuery - Data files can be uploaded from local sources, Google Drive, or Cloud Storage buckets, using BigQuery Data Transfer Service (DTS), Cloud Data Fusion plugins, by replicating data from relational databases with Datastream for BigQuery, or by leveraging Google's data integration partnerships.Screenshot of generative AI use cases with BigQuery and Gemini models - Data pipelines that blend structured data, unstructured data and generative AI models together can be built to create a new class of analytical applications. BigQuery integrates with Gemini 1.0 Pro using Vertex AI. The Gemini 1.0 Pro model is designed for higher input/output scale and better result quality across a wide range of tasks like text summarization and sentiment analysis. It can be accessed using simple SQL statements or BigQuery’s embedded DataFrame API from right inside the BigQuery console.Screenshot of insights derived from images, documents, and audio files, combined with structured data - Unstructured data represents a large portion of untapped enterprise data. However, it can be challenging to interpret, making it difficult to extract meaningful insights from it. Leveraging the power of BigLake, users can derive insights from images, documents, and audio files using a broad range of AI models including Vertex AI’s vision, document processing, and speech-to-text APIs, open-source TensorFlow Hub models, or custom models.Screenshot of event-driven analysis - Built-in streaming capabilities automatically ingest streaming data and make it immediately available to query. This allows users to make business decisions based on the freshest data. Or Dataflow can be used to enable simplified streaming data pipelines.Screenshot of predicting business outcomes AI/ML - Predictive analytics can be used to streamline operations, boost revenue, and mitigate risk. BigQuery ML democratizes the use of ML by empowering data analysts to build and run models using existing business intelligence tools and spreadsheets.