"Sagas", or distributed transactions, are what you're looking for. These are API... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		jjanyan on Nov 28, 2019 \| parent \| context \| favorite \| on: Ask HN: How do you deal with atomicity in microser... "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.

c89X on Nov 28, 2019 [–]

That's it! Not sure how I never stumbled upon this. Thanks!

manasvi_gupta on Nov 28, 2019 | [–]

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.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact