Hi Lakmal, And quoting Chris "sounds like we are moving towards the Actor model (use a central message box and multiple actor subscribers). how are we going to identify how to scale out the actors? maybe make the actors stratos hosted services and write auto-scaling rules per flight? How does stratos gauge a load based on 'pulls' versus the current model which counts pushed messages? "
This approach will make everything pulled at the core of AF. As Chris highlights there are, many areas we have to look at, especially when scaling and load balancing. This includes entries partitioning as well. Multiple subscribers can partitioned or topics can be partitioned I believe each node needs to be studied and knowing best practices will help a lot. Out of many possible solution would be to have Jenkins bucket as topics and they will be pulled by Jenkins. We are not even thinking on working no this model yet ... but we'll have a wider architectural discussion with you included. thanks, dimuthu On Wed, Apr 29, 2015 at 1:03 PM, Lakmal Warusawithana <[email protected]> wrote: > +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 > > -- 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
