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
- SurrealDB 4 launches as multi-model ACID database for the agentic era — Scobleizer · 2026-11-04
- Fire at Taiwan Panasonic PCB materials plant may tighten CCL supply further — zephyr_z9 · 2026-11-04
- AMD CEO Lisa Su says revenue to grow over 80% in 2027, data center to top 80% of sales — AccBalanced · 2026-11-04
- Same Claude model served by Bedrock one day and Anthropic the next, dev finds — georgos_pappas · 2026-11-04
- Self-improving software is inevitable: closing the agent-observability loop — bibryam · 2026-11-04
- Gigabyte's AI TOP motherboard packs 2TB RAM and 9 GPUs for home AI labs — vincent_koc · 2026-11-04