Embedded Files
Why AutoBUS ?
Why AutoBUS ?
With increased use in microservices architecture, several observations have been made about classical message brokers :
With increased use in microservices architecture, several observations have been made about classical message brokers :
In microservices that communicate with each other, several messages are sent one after the other, or even simultaneously. It is common for messages to get lost due to a fault in the execution of a microservice, and thus the flow is broken.
More problematic still, it is necessary to find where the chain is broken to restart the process. However, it is never easy to browse the logs of all the servers hosting the microservices. It takes time and the quality of service is therefore not there.
It is possible to create a flow routing microservice, however this creates an increase in messages passing through your bus. This complicates the operation of your environment.
It is not easy to have a clear visibility of the communications between microservices. Certainly it is possible to document and refer to it. But how can you be sure of what is actually transiting on the bus ?
It is thus and by these observations that AutoBUS was born.
It is thus and by these observations that AutoBUS was born.
It was necessary to create a bus that could manage the flow of messages. And therefore, integrate a workflow directly into the bus.
It was necessary to create a bus that could manage the flow of messages. And therefore, integrate a workflow directly into the bus.
The flow logic has therefore been reassigned where it should, in the message broker. That's why a web manager has been added, you can build and view all the streams you want to pass.
The flow logic has therefore been reassigned where it should, in the message broker. That's why a web manager has been added, you can build and view all the streams you want to pass.
It is now easy to find the break in the processing chain, it is easy to visualize in the stream where the blocking element is. The flow is displayed on the interface and the defective part is highlighted. Increased responsiveness also thanks to the notification.
It is now easy to find the break in the processing chain, it is easy to visualize in the stream where the blocking element is. The flow is displayed on the interface and the defective part is highlighted. Increased responsiveness also thanks to the notification.
Page updated
Google Sites
Report abuse