infoq 读书笔记-Resilience in Deep Systems

本文主要是介绍infoq 读书笔记-Resilience in Deep Systems，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！

1.Service granularity Don’t go with the hype; correspond to a real business capability. When designing complex applications using microservice architecture,we’re looking to define a set of
cohesive and loosely-coupled services.

we found that defining microservices that correspond to a real business capability will result in a sane amount of selfcontained pieces of business functionality. Those pieces can still be very cohesive, loosely
coupled, scale well, be testable, built, and owned by a small enough team.

2.Sharing data - safe and consistent Be Aware: The worst monolith you can have is a distributed monolith.
However, using synchronous communications, like REST, across the entire deep system makes the various components in the chain very tightly coupled to each other. It creates an increased dependency on the network’s reliability.

In reality, we found that such a deep system behaves more like a monolith, or more precisely a distributed monolith, which prevents the full benefits of microservices from being enjoyed.

Using an asynchronous, event-driven architecture enables your microservices to publish fresh data updates to other microservices.
However, by using “push” instead of “pull,” the system can handle data updates in almost real-time and dispose of all that overhead.

3.Distributed storytelling Don’t lose sight of the flow of events; increase observability. Observability isn’t just knowing that a problem is happening, but knowing why it is happening.
The growing amount of microservices layers and their logged data is challenging for both R&D teams and business analysts.