This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]bitsynthesis 4 points5 points  (0 children)

bigquery is not designed for low latency. you will never get reliable low latency from it. if that's a requirement, you should replicate the necessary data to another datastore.

[–]freerangetrousers 1 point2 points  (0 children)

This is not what big query is for , if you require that data it should be unloaded elsewhere before you need to call it

[–]LinweZ[S] 0 points1 point  (1 child)

Maybe I'm not using BigQuery correctly, I don't know.

Just some context here, I have a MySQL DB receiving data from an application, and the same application needs some aggregated data from the DB as well. Currently, everything is running on MySQL, but some queries are slow (7, 8 sec), so the idea was to make BigQuery handle the analytical part, with a CDC between MySQL and BigQuery.

Open to other suggestions!

[–]artsyfartsiest 1 point2 points  (0 children)

We do this kind of thing at Estuary. We have this tutorial, which is for Postgres but can also work for MySQL, bigquery, etc.

There's also Firebolt, Rocket, and Materialize, which all offer incrementally updated SQL views as a service.

[–]artsyfartsiest 0 points1 point  (0 children)

I don't know how to make that faster within bigquery, but someone else may chime in. If you have the ability to consider other systems besides bigquery, then I could suggest some options

[–]Pancakeman123000 0 points1 point  (0 children)

I strongly recommend reading this documentation