Explore chapters and articles related to this topic
Distributed Systems
Published in Vivek Kale, Digital Transformation of Enterprise Architecture, 2019
The main advantage of such an architectural style is that it fosters the development of open systems: new modules can be added and easily integrated into the system as long as they have compliant interfaces for registering to the events. This architectural style solves some of the limitations observed for the top-down and object-oriented styles: The invocation pattern is implicit, and the connection between the caller and the callee is not hard-coded; this gives a lot of flexibility since addition or removal of a handler to events can be done without changes in the source code of applications.The event source does not need to know the identity of the event handler in order to invoke the callback.
Distributed Systems
Published in Vivek Kale, Enterprise Process Management Systems, 2018
The main advantage of such an architectural style is that it fosters the development of open systems: new modules can be added and easily integrated into the system as long as they have compliant interfaces for registering to the events. This architectural style solves some of the limitations observed for the top-down and object-oriented styles: The invocation pattern is implicit, and the connection between the caller and the callee is not hard-coded; this gives a lot of flexibility since the addition or removal of a handler to events can be done without changes in the source code of applications.The event source does not need to know the identity of the event handler in order to invoke the callback.
Distributed Systems
Published in Vivek Kale, Agile Network Businesses, 2017
The main advantage of such an architectural style is that it fosters the development of open systems: new modules can be added and easily integrated into the system as long as they have compliant interfaces for registering to the events. This architectural style solves some of the limitations observed for the top-down and object-oriented styles. The invocation pattern is implicit, and the connection between the caller and the callee is not hard coded; this provides a lot of flexibility, since the addition or removal of a handler to events can be done without changes in the source code of applications.The event source does not need to know the identity of the event handler in order to invoke the callback.
Do we need to pay technical debt in blockchain software systems?
Published in Connection Science, 2022
Yubin Qu, Tie Bao, Xiang Chen, Long Li, Xianzhen Dou, Meng Yuan, Hongmei Wang
=expected_timeout_logs): sleep(3)”. In the original source code, a hard-coded method was used to wait for five seconds to confirm the closure of other connected nodes. Due to complex network conditions, there may be cases where the connection node fails to close. In this case, application developers need to perform specific software tests. This issue is reported and has been merged in GitHub .25 In the fixed source code, the node is disconnected more gracefully by using the method of waiting to be closed.