News for hackers. Stuff that matters.

A comment on Ask HN: How do you deal with atomicity in microservice environments?.

Re:Ask HN: How do you deal with atomicity in microservice en... by jjanyan on Thursday November 28, 2019 @08:30AM (#21657151)
"Sagas", or distributed transactions, are what you're looking for. These are APIs/functions/methods that know how to complete every step of your atomic operation and how to roll it back if any step fails. They more or less recreate what would have been a single database transaction pre-microservice.
[ Parent | on HN ]
Re:Ask HN: How do you deal with atomicity in microservice en... by c89X on Thursday November 28, 2019 @09:27AM (#21657566)
That's it! Not sure how I never stumbled upon this. Thanks!
[ Parent | on HN ]
Re:Ask HN: How do you deal with atomicity in microservice en... by manasvi_gupta on Thursday November 28, 2019 @03:25PM (#21659967)
Came here to say same thing. Saga pattern is the way to go.

Also, suggest you to carefully think about transaction boundaries, if possible, prefer eventual consistency over transactions.

[ Parent | on HN ]