Google Cloud adds native transactional queues to Spanner for in-database async work
rseroter · x · 2026-09-19
Google Cloud added native queues to Spanner, bringing transactional messaging into the database for scheduling and long-running in-database work.
- Messages can be sent and acknowledged atomically within a Spanner transaction alongside other writes; failed transactions roll back enqueued messages
- Pull-based consumption via a SQL interface; small user-defined payloads that scale with instance compute
- vs. change streams: queues suit transactional event notifications, future-scheduled work, and per-message acks; change streams suit high-throughput replication, cache/index sync, and audit logging (up to 10MB fragments, with heartbeats and checkpointing)
Key benefit: no separate messaging infrastructure to provision and manage, simplifying architecture and cutting costs.
More from Infra
- HEIF Heist: one C image parser bug chain leads to RCE in OpenAI, Meta, GitHub — ccerrato147 · 2026-09-19
- Turbo-dLLM Open-Sources CSBP, Speeding Diffusion LLM Training Up to 7.59x at 1M Context — Azaliamirh · 2026-09-19
- Luminal runs large-scale FLUX.2 diffusion on AMD MI300X to cut cost per image — ycombinator · 2026-09-19
- Virginia governor creates AI task force and moves to restrain data centers — The Verge AI · 2026-09-19
- AI Infra Summit: Penguin Solutions and Astera Labs Bet Big on CXL Memory Expansion — BenBajarin · 2026-09-19
- Jev seen as local-model stand-in for low-latency apps; open-weight RLCD models expected — HankYeomans · 2026-09-19