Hi All, Currently transports (AMQP,MQTT) in MB are coupled with the andes core (same bundle). We're in process of identifying a way to abstract the transports from its core, so that we bring in a pluggable architecture which would allow plug in the relevant transport to the broker on demand. This will help to featherweight MB.
The abstract message flow would look like the following, [image: Inline image 2] As depicted in the above diagram, if the transport is abstracted into a separate bundle, there will be circular dependency between the core and the transport. i.e when messages are published 'transport' will need to call services in the 'core' and when messages are distributed to the subscribers the 'core' will need to call services in the 'transport' Currently we're in the process of identifying a solution for the circular dependency, making the cardinality of one of the referencing service optional [1] could be a solution, but we need to understand whether there's a better approach for this. WDYT ? [1] http://docs.spring.io/osgi/docs/current/api/org/springframework/osgi/service/importer/support/Cardinality.html Thanks, Pamod -- *Pamod Sylvester * *WSO2 Inc.; http://wso2.com <http://wso2.com>* cell: +94 77 7779495
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
