3 ms·
As far as I understand microservices, these kind of issues must be solved by your architecture. Either the service is atomical, or the orchestration of your ser
by valevk 12y ago
As far as I understand microservices, these kind of issues must be solved by your architecture. Either the service is atomical, or the orchestration of your services must be in "flow", where no race conditions should occur.
- amelius 12y agoIt sounds like this is a difficult path to take. Especially considering the fact that, usually, system requirements may change over time.
- tekacs 12y agoIt absolutely is. It's for exactly these reasons why only highly organised and qualified teams tend to have substantial microservice deployments today. It's also why I think[1] we need to start building a framework[2] to provide standardised solutions (or at least patterns) to some of these problems. [1]: https://vimeo.com/118895501 https://vimeo.com/118895501 [2]: http://wym.io/ http://wym.io/