Ford has a customer-facing application. We use BigQuery to keep multiple metric records of Ford motors. Ford uses BigQuery to store huge customer data regarding a vehicle's uptime, downtime, velocity, etc. They save this data using BigQuery instead of the normal database.
The solution is very useful nowadays for keeping a huge number of records. It's easy to maintain. Since it has a columnar storage data format, BigQuery is more useful to provide the analytical details. BigQuery can be used to perform some analytical activity over the data.
Nowadays, AI and data analytics projects use a columnar data approach. This will help achieve filtration and analyze data presented in a table format. It is very useful to provide the analytical data. Since it is provided over the cloud, its SLA value is more than 99.9%, and it provides high availability.
Since I used BigQuery over the GCP cloud environment, I'm not sure whether we can go through internal IDEAs like IntelliJ or DBeaver that we use to connect with databases. Instead of connecting directly to BigQuery, we connect to GCP, Cloud Run, and then to BigQuery, which is a long process.
Sometimes, we face some issues, bugs, and defects. We must first connect with a VPN to check data issues while working from home. Then, it allows you to connect to the cloud. After logging into the cloud, it searches for the service we are looking for, and then we go to BigQuery. This is a long process.
After that, we analyze the issues in a table. Instead, it would be very helpful if it could provide a tool that we can install on our MacBook or Windows system. Once we open this tool, we can connect directly to the BigQuery server and easily perform tasks.
I have been using BigQuery for two years.
I rate the solution’s stability a nine out of ten.
Scalability deals with several instances of how we are going to use it. It also considers the number of slots needed to execute the job. BigQuery is very useful for scaling the data. It depends on the users and how frequently data is going to be used with the auto-scaling part.
I did not face any challenges while implementing and configuring BigQuery because I have experience with RDBMS and NoSQL.
There are different databases like BigQuery, Oracle, MySQL, and PostgreSQL. These are just flavors, but the goal is to store the data. We are changing the flavor called BigQuery. It is part of the database, but some of the structure will change, and some analytical activity will be added or improved.
BigQuery is more powerful than the earlier version. Some people use Bigtable, while others use BigQuery. It depends on their use cases. Bigtable is a NoSQL that provides structured data and unstructured data. If we are going for structured data, BigQuery is more powerful and provides analytical activity.
I would recommend BigQuery to other users because it will be helpful for AI and analytics related things. The updated technologies we use and analytical activities we perform should be updated.
Overall, I rate the solution a nine out of ten.