+1 Dimuthu, this will provide more resilient to the architecture. When going with pub/sub, message bus event driven architecture there are some good practices you may need to think about. If you folks want, we can arrange a meeting to discuss what we learnt from Stratos implementation.
On Wed, Apr 29, 2015 at 5:36 AM, Dimuthu Leelarathne <[email protected]> wrote: > Hi all, > > This has been a talking-point among all who are interested in App Factory. > Right now all communication happen over HTTP, and we use BPEL to provide > extensibility and governance. > > During couple of brain storm sessions we were thinking of using pub/sub > architecture with MB to avoid failures and achieve stability. If we publish > events to topics we can achieve extensibility but what about governance. > Will there be BPEL and JMS living together? What would be the most elegant > simple model. To overcome that we could use the following methodology (I > have attached the image) > > > > > The above architecture would give the governance properties of BPEL. > Basically the governance service does nothing if it doesn't have any BPELs > registered and simply publishes "Approved" topic. Once Approved topic is > there Git repo is created, Jenkins job is created and etc .... > > thanks, > dimuthu > > > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile : 0773661935 > > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Lakmal Warusawithana Vice President, Apache Stratos Director - Cloud Architecture; WSO2 Inc. Mobile : +94714289692 Blog : http://lakmalsview.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
