Re:Give Me Back My Monolith
by qaq on Wednesday March 13, 2019 @05:05PM
(#19383773)
The question is transaction boundaries try unrolling a change that had to touch state of several services and one of the requests failed
[ Parent
| on HN ]
Right, because we write against DynamoDB/Etcd transactions were a non-option anyways, and we only have CompareAndSwap as a locking primitive
https://github.com/gravitational/teleport/blob/master/lib/ba...
In addition to that Golang's context
https://golang.org/pkg/context/
is used to broadcast the failure of a distributed operation and release associated resources with it
DynamoDB has transactions now.
https://aws.amazon.com/blogs/aws/new-amazon-dynamodb-transac...
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.
https://docs.aws.amazon.com/amazondynamodb/latest/developerg...