Google Cloud launches Spanner queues to give AI agents transactional messaging

Google Cloud announced on October 2, 2026, that Spanner queues are now generally available. The feature brings native transactional messaging into Spanner, the company’s distributed database. What Spanner queues actually do Developers can now create a message inside a standard read-write transaction in Spanner. That means a database update and a queued task can land together in one commit. Google frames this as an atomic “decide-and-act” operation. The feature includes several core capabilities: Atomic enqueue operations: messages are created as part of a Spanner transaction, so they commit or roll back alongside the data they relate to. Scheduled delivery: messages can be set for delivery at a later time rather than immediately. Exactly-once processing semantics: each message is meant to be handled once, not dropped and not duplicated. Per-message acknowledgment: consumers confirm each message individually after processing it. Pull-based consumption via SQL: applications fetch messages using the same query language they already use against the database. Transactional messaging also carries over Spanner’s consistency guarantees, specifically strict serializability and external cons...