We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4
GCP: BigQuery Adoption
Source - https://cloud.google.com/docs Google Cloud Platform : Cloud Training
➤ Discussion on Case Study of a Pharma Company :
➤ Existing DB : Postgres ➤ Machine : Quad-Core CPU, 16GB RAM ➤ Other Solutions - ➤ Vertical Scaling of Server ➤ Using Alternate DBs ➤ Using No-SQL DBs ➤ Final Service : BigQuery Google Cloud Platform : Cloud Training
➤ When It Makes Sense to Use BigQuery
➤ Use it when you have queries that run more than five seconds in a relational database. ➤ BigQuery is suitable for “heavy” queries, those that operate using a big set of data. The bigger the dataset, the more you’re likely to gain performance by using BigQuery. ➤ Not Suitable for Data Aggregation queries. ➤ BigQuery doesn’t like joins, so you should merge your data into one table to get better execution time. ➤ BigQuery is good for scenarios where data does not change often and you want to use cache, as it has built-in cache. What does this mean? If you run the same query and the data in tables is not changed (updated), BigQuery will just use cached results and will not try to execute the query again. Also, BigQuery is not charging money for cached queries. ➤ You can also use BigQuery when you want to reduce the load on your relational database. Analytical queries are “heavy” and overusing them under a relational database can lead to performance issues. Will see you in Next Lecture…