Database / Google Spanner Database Interview questions
When should you use change streams in Spanner?
Change streams capture row-level insert, update, and delete activity on watched tables (or the whole database) in near real time, ordered and partitioned by commit timestamp, without the application having to write custom trigger logic or poll for changes.
CREATE CHANGE STREAM OrderChanges FOR Orders;
They fit scenarios like replicating changes into BigQuery for analytics, invalidating caches when underlying rows change, driving event-driven microservices off database mutations, or building audit trails that need the exact sequence of changes rather than just a periodic snapshot. Because change streams read through the same transactional, externally consistent commit log Spanner already maintains, they avoid the missed-update or duplicate-event problems common with naive polling approaches, and Dataflow provides ready-made connectors for consuming them into downstream systems.
More Related questions...
