I guess we are not talking about just the create application right? If we go
with this it will apply to versioning, build, deploy, promotion, demotion,
etc.. Right?
Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
From: Dimuthu Leelarathne
Sent: Wednesday, April 29, 2015 5:36 AM
To: architecture, Sanjiva Weerawarana
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
