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.
$6.25
per TiB (after the 1st 1 TiB per month, which is free)
Vertex AI
Score 8.6 out of 10
N/A
Vertex AI on Google Cloud is an MLOps solution, used to build, deploy, and scale machine learning (ML) models with fully managed ML tools for any use case.
$0
Starting at
Pricing
Google BigQuery
Vertex AI
Editions & Modules
Standard edition
$0.04 / slot hour
Enterprise edition
$0.06 / slot hour
Enterprise Plus edition
$0.10 / slot hour
Imagen model for image generation
$0.0001
Starting at
Text, chat, and code generation
$0.0001
per 1,000 characters
Text data upload, training, deployment, prediction
$0.05
per hour
Video data training and prediction
$0.462
per node hour
Image data training, deployment, and prediction
$1.375
per node hour
Offerings
Pricing Offerings
Google BigQuery
Vertex AI
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
Pricing is based on the Vertex AI tools and services, storage, compute, and Google Cloud resources used.
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 …
I have used OpenAI for their LLM and Vector Embedding service, they are really good at it. But Vertex AI has other better services like training pipeline , depolyment creation etc.
Event-based data can be captured seamlessly from our data layers (and exported to Google BigQuery). When events like page-views, clicks, add-to-cart are tracked, Google BigQuery can help efficiently with running queries to observe patterns in user behaviour. That intermediate step of trying to "untangle" event data is resolved by Google BigQuery. A scenario where it could possibly be less appropriate is when analysing "granular" details (like small changes to a database happening very frequently).
we used Vertex AI on our automation process the model very useful and working as expected we have implemented in our monitoring phase this very helpful our analysis part. real time response is very effective and actively provide detailed overview about our products.this phase is well suited in our org. this model could not applicable for small level projects why because this model not needed for small level projects and without related resource of ML this model not useful. strictly on non cloud org not suitable means on pram not suitable
GSheet data can be linked to a BigQuery table and the data in that sheet is ingested in realtime into BigQuery. It's a live 'sync' which means it supports insertions, deletions, and alterations. The only limitation here is the schema'; this remains static once the table is created.
Seamless integration with other GCP products.
A simple pipeline might look like this:-
GForms -> GSheets -> BigQuery -> Looker
It all links up really well and with ease.
One instance holds many projects.
Separating data into datamarts or datameshes is really easy in BigQuery, since one BigQuery instance can hold multiple projects; which are isolated collections of datasets.
Vertex AI comes with support for LOTs of LLMs out of the box
MLOps tools are available that help to standardize operational aspects
Document AI is an out of the box feature that works just perfectly for our use cases of automating lots to tedious data extraction tasks from images as well as papers
Please expand the availability of documentation, tutorials, and community forums to provide developers with comprehensive support and guidance on using Google BigQuery effectively for their projects.
If possible, simplify the pricing model and provide clearer cost breakdowns to help users understand and plan for expenses when using Google BigQuery. Also, some cost reduction is welcome.
It still misses the process of importing data into Google BigQuery. Probably, by improving compatibility with different data formats and sources and reducing the complexity of data ingestion workflows, it can be made to work.
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.
I think overall it is easy to use. I haven't done anything from the development side but an more of an end user of reporting tables built in Google BigQuery. I connect data visualization tools like Tableau or Power BI to the BigQuery reporting tables to analyze trends and create complex dashboards.
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.
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.
Google is always top notch with their security and user interface performance. We use Google's entire suite in our business anyways, so using Vertex became second nature very quickly. I will say, though, that Google does need to come down on the price somewhat with their token allocation. Also, their UI is very robust, so it does require some time for training to really master it.
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.
PowerBI can connect to GA4 for example but the data processing is more complicated and it takes longer to create dashboards. Azure is great once the data import has been configured but it's not an easy task for small businesses as it is with BigQuery.
We tend to adapt and use the platform that suits the customers needs the best. We return to Vertex AI because it is the most in-depth option out there so we can configure it any which way they want. However, it is not quick to market and constantly changing or updating it's feature-set. This makes it suitable for bigger customers that have the capital and time to spend on a bigger project that is well researched and not quick to market like some of the other options that feel like a light-version of this.
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.
Google Support has kindly provide individual support and consultants to assist with the integration work. In the circumstance where the consultants are not present to support with the work, Google Support Helpline will always be available to answer to the queries without having to wait for more than 3 days.
Previously, running complex queries on our on-premise data warehouse could take hours. Google BigQuery processes the same queries in minutes. We estimate it saves our team at least 25% of their time.
We can target our marketing campaigns very easily and understand our customer behaviour. It lets us personalize marketing campaigns and product recommendations and experience at least a 20% improvement in overall campaign performance.
Now, we only pay for the resources we use. Saved $1 million annually on data infrastructure and data storage costs compared to our previous solution.
