|
|
|
|
|
|
by jamestenglish
3473 days ago
|
|
|
This was poorly worded on my part, Kubernetes does not in anyway solve this problem. Instead I meant to use Kubernetes as an example of the work being done to standardize and abstract these sorts of microservice issues. Kubernetes solves a lot of orchestration issues and I expect there will be greater work with other projects into solving other problems like distributed transactions in the future. The current thoughts on microservices is that you should really re-evaluate how critical strong transnational guarantees really are to your application. |
|
|
Are there some examples of what else one can do?
I'm generally fine with service 2 eventually being called if service 1 is, but then I need that to happen.
e.g. I have a payment service and an internal "subscriptions service". If user requests a refund, I have to both issue refund to payment service and cancel internal subscription