Hacker News Reader

The question is transaction boundaries try unrolling a change that had to touch state of several services and one of the requests failed

Right, because we write against DynamoDB/Etcd transactions were a non-option anyways, and we only have CompareAndSwap as a locking primitive

In addition to that Golang's context

is used to broadcast the failure of a distributed operation and release associated resources with it

DynamoDB has transactions now.

It's probably closer to multi-writes though, than transactions in a classic sense, but good improvement nevertheless.

It's a real transaction like MySQL or PG.