Hi, I have done the $subject, and this was be mainly focused to provide below objectives.
- Unifying all different kind of datapublishers (LoadbalancingDatapublisher, AsyncDatapublisher, Datapublisher) currently available and provide one Datapublisher. - Implement data publisher endpoint as extensible, so that a new Endpoint type can be added; by default thrift, and binary is supported. - Removing the complications introduced due to improving the data publisher to provide load balancing and fail over functionality. The details on how to use the refactored data publisher has been explained in [1]. Please note with this change, we also have removed the defineStream and findStream operation from the data publisher (ie, client from the client side), and we have moved these operations to the receiver side (BAM/CEP) as discussed in earlier discussions. The users can define the stream with toolboxes, or with Event streams UI [2] in the management console. Furthermore during this effort there wasn't any changes introduced on the receiver side (BAM/CEP), and hence old Datapublishers will continue to work with new BAM 3.0 and CEP 4.0 which is yet to be released. Hence old clients (APIM, ESB, etc), can send the events to new BAM/CEP without any problem.Also as far as the streams are defined in older BAM/CEP via toolboxes, or even streams UI, the new refactored data publisher also will work with old BAM/CEP. [1] https://docs.wso2.com/display/BAM300/Data+Publisher [2] https://docs.wso2.com/display/BAM300/Event+Streams Thanks, Sinthuja. -- *Sinthuja Rajendran* Senior Software Engineer <http://wso2.com/> WSO2, Inc.:http://wso2.com Blog: http://sinthu-rajan.blogspot.com/ Mobile: +94774273955
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
