News for hackers. Stuff that matters.
Re:Ask HN: How do you deal with atomicity in microservice en... by mooted1 on Thursday November 28, 2019 @04:17PM (#21660249)
Also, I think the answers you're getting keep telling you to build distributed transactions because

a.) they didn't read your post and are overindexing on "microservices" b.) this isn't an atomicity problem, it's a workflow problem. When people say atomicity, they're usually referring to operations over data. In your case, it sounds like you need a way to coordinate execution of side-effectful operations (like creating a charge).

Re:Ask HN: How do you deal with atomicity in microservice en... by LoSboccacc on Thursday November 28, 2019 @04:54PM (#21660433)
but, when one starts talking about idempotence and retries the first thing that comes to mind is these are just user mediated two phases commits, where an error dialog and user interaction drive the phases instead of a distributed transaction system, by which point one can just cut the middleman and build the thing out of tested and robust components
Re:Ask HN: How do you deal with atomicity in microservice en... by mooted1 on Thursday November 28, 2019 @06:04PM (#21660750)
What middleman do you want to cut out? My proposal doesn't add any dependencies. It's also not possible to prevent duplicate charges if a user POSTs a form twice without idempotency keys, so idempotency is necessary.

I'm really not sure what you're actually proposing?

Re:Ask HN: How do you deal with atomicity in microservice en... by LoSboccacc on Friday November 29, 2019 @01:11AM (#21662429)
the user doing the retries