Thanks for your reading and for the comment.

You have right in some use cases, it’s wrong for others.

Mine was about IoT devices, water meter, with more than 3 millions of device that provides 35+ metrics every hours. The power of BigQuery to aggregate the data and extract the value was the key. But for low latency, it was an issue. Therefore, we extracted only the aggregated value to put them in Cloud SQL and serve them at low latency, while the data warehouse was still in BigQuery. And it’s far less expensive that Spanner for Tb of immutable data!

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

guillaume blaquiere
guillaume blaquiere

Written by guillaume blaquiere

GDE cloud platform, Group Data Architect @Carrefour, speaker, writer and polyglot developer, Google Cloud platform 3x certified, serverless addict and Go fan.

No responses yet

Write a response