Hi all, *Problem* In current Ballerina Message Broker, there is no proper mechanism to trigger events on scenarios like queue full, queue empty, queue limit reached, consumer added etc.
*Proposed Solution* My project is to develop a module that listens for those events in the Message Broker and publish the event data to a registered medium such as Message Broker where clients can access those data. In my project I will implement a publisher which can publish notifications to a defined exchange in the Message Broker. And my module can be further extended to include other publishers. In the Solution there is an, 1. *Event Publisher* which can be used to publish the event data to the intended medium 2. *Event Service Generator* which finds the user intended implementations of *Event Publisher* and includes them in the broker functions 3. *Event Manager *which listens for events in the broker and use *the registered Event Publisher *to publish event data I have studied the functionality of the Ballerina Message Broker and developed 3 sequence diagrams in the below attachments for my project. -- *Kasun Perera* *Software engineering Intern* WSO2 (University of Moratuwa) *mobile *: *+94 712461670* | *email *: [email protected]
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
