This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
Message passing between agents in a distributed environment is required. Any kind of protocol can suffice for this. Some networking systems like to use open source in this regard while others build on message queuing.
Every network prepares for fault tolerance. Since faults can occur in a domain, temporarily or permanently, each component determines which activities to perform and how to overcome what is not available.
Fault domains are a group covering known faults in an isolation. Yet some faults may occur in combinations. It is best to give names to patterns of faults so that they can be included in the design of components.
Data-driven computing has required changes in networking products. While previously, online transactional activities were read-write intensive and synchronous, today most processors including order and payments are done asynchronously on data-driven frameworks usually employing a message queueing. Networking products do better with improved caching for this processing.
The latency involved in the execution of an order and the prevention of repeats in the order processing has not been relaxed. A gift card run through a store register for renewing must make its way to the backend networking so that it is not charged again when run through and before the prior execution is completed. A networking based product such as message queue should not require a database with strong ACID guarantees but it should support serialized readability against all read-write operations
No comments:
Post a Comment