@InfoQ on #Microservices
microservice architectural pattern is best used for implementing the "breadth" of business functionality. Engineers should avoid building deep call chains of services, as this can increase the probability of failure 1/2
Deep chains in #Microservices can also increase the challenges of locating and diagnosing issues. Code libraries can often be used more effectively to implement "depth" within services.
Good advice for #architects dealing with issues. Thanks @InfoQ 2/2
#developers should avoid building highly-coupled distributed #systems. Instead, they should build "resilient federations" based on standard domain-driven design (DDD) federations of services for implementing #Microservices
#Developers should invest heavily in compensation strategies in #code; "if something doesn't work quite right, make it so that the service degrades instead of failing" during implementation of #Microservices
Degrade rather than fail.
In order for progress to be made in building effective software systems powered by #Microservices within the larger industry context, it is important that the conversations focusing on #architecture also show what didn't work in addition to highlighting the benefits
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.