3 ms·
"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 operatio
by jjanyan 7y ago
"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 7y agoThat's it! Not sure how I never stumbled upon this. Thanks!
- manasvi_gupta 7y agoCame 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.