Best Serverless SQL Database
Overall Satisfaction with Google BigQuery
We use BigQuery as the company's Data Warehousing tool. The transactional information is handled mostly in Firebase and we inform BigQuery of each update or creation event from which we build the status and history tables. In addition, we use it to consolidate data from other external sources, such as Facebook, Analytics, Google Ads, among others.
Pros
- Data Warehousing
- Sporadic SQL queries without having to manage instances
- Reporting directly consumed from views
Cons
- A better output data exploration tool
- Better handling of parquet files
- An own application with a more comfortable UI than in the browser
- Cost per consumption
- Serverless
- Simple and intuitive UX
- Development of dashboards and reports at a very low cost
- Execution of automatic rules in Firebase from queries in Bigquery
BigQuery has a simpler and more intuitive user experience (as is the case with most of its products) compared to AWS, which has a more technical and complex profile, so it was the first tool we used. It's still my go-to option for handling SQL queries, though it doesn't detract from Athenas if the rest of the infrastructure is on AWS.
Do you think Google BigQuery delivers good value for the price?
Yes
Are you happy with Google BigQuery's feature set?
Yes
Did Google BigQuery live up to sales and marketing promises?
Yes
Did implementation of Google BigQuery go as expected?
Yes
Would you buy Google BigQuery again?
Yes
Comments
Please log in to join the conversation