BigQuery Streaming Inserts
A charge for rows written through the streaming insert path or the Storage Write API in default mode. The thing worth knowing is the alternative: batch loads into BigQuery are free, so this charge is entirely a payment for immediacy.
Billed: Per gibibyte of data streamed in. Batch loading the same data costs nothing.
What triggers this charge
- insertAll / tabledata.insertAll calls from an application.
- Storage Write API in default (streaming) mode.
- Dataflow pipelines writing to BigQuery with streaming inserts enabled — often the default in a template nobody changed.
- Log sinks routing directly into BigQuery.
How to reduce it
Ask whether seconds actually matter
Most "real-time" dashboards are looked at hourly. Micro-batching into five-minute loads moves the data onto the free batch path with no perceived difference.
Use the Storage Write API in pending mode
Pending mode gives transactional batch semantics through the modern API and is billed differently from the default streaming path.
Buffer through Pub/Sub and load on a schedule
Where the source must push continuously but the consumer does not need it instantly, a buffer converts a streaming charge into a batch load.
Rates
Now find out how much of this you are actually paying.
Finitizer breaks your Google Cloud bill down to the SKU, shows how each one has moved since last week, and separates rate changes from usage changes — so you know whether to talk to engineering or to procurement.