Is there a design pattern or practice I can use to help with services that are either down or go down, while others are stable?What if I have three microservices, and two of them are good, and one dies right in the middle of a POST?  Two will get the POST and one will not.  I don't think I can do transactions because I'm shipping off my requests to a service.How do I design for that?  I don't want orphan data in various databases.
How do you design your software that updates several microservices, if one of them fails?
database;concurrency;microservices;data integrity