The more distributed a software system is designed, the more you should think about resilience. Because of the distribution, calling the involved communication partners can and will often lead to errors. In order to keep the effects of these errors as small as possible, or to avoid them completely, it has become the norm to work with the necessary resilience patterns. But what is the right approach for dealing with resilience? A service mesh tool or a framework? Both approaches have their pros and cons.
Ihnen gefällt vielleicht auch
Artikel auf JAXenter
Artikel im JavaMagazin 4.20
Interview mit Michael Hofmann (JAXenter 2019)
Artikel im Entwickler Magazin 06.2019 - Istio