Hacker News new | ask | show | jobs
by sandGorgon 2633 days ago
Hmm..I would prefer to not have it. In production, managing database persistence is very hard. Especially when you go down the kubernetes road.

I would take higher latency, but avoid pulling in a whole database infrastructure.

Plus a huge number of us use postgresql..so that becomes another set of a mess. I would strongly urge you to do this on the same bigquery database that you would connect to anyways.

1 comments

Bigquery exists only in Google Cloud. This is a columnar database like Redshift. It is not designed for fast processing small queries that are necessary to support the operation of any application. Its main feature is that it can scale the execution of heavy analytical queries between 10,000 nodes transparently for the end user. Users have no control over Bigquery instances. This is super cost effective cloud analytical database as a service to be used as centralized data warehouse for company of any size.