Hi Udara, +1 if this fits better the paradigm to store relevant information.
One quick question, how will this change the sequence flow in cases like group deployment, octl restart (restoring the grouping model), etc …. ? As you mentioned, CC (and any “module”) involved needs to be able to access the store grouping information via the relevant API, Thanks Martin From: isu...@wso2.com [mailto:isu...@wso2.com] On Behalf Of Isuru Haththotuwa Sent: Wednesday, July 23, 2014 7:21 PM To: dev Cc: Lakmal Warusawithana; Udara Liyanage; Martin Eppel (meppel); Reka Thirunavukkarasu Subject: Re: Composite App - Where to store service groups Hi Udara, On Wed, Jul 23, 2014 at 11:49 AM, Udara Liyanage <ud...@wso2.com<mailto:ud...@wso2.com>> wrote: Hi, With the current implementation, service groups are stored in SM. When a CompositeApp is deployed, group details and composite app details should be sent to CC and then CC fire ApplicationCreatedEvent event with those details again. My suggestion is to store the service groups in AS, then only the meta data are needed to be sent from SM->CC and in ApplicationCreatedEvent. My main concern is AS is the one that works with the groups more , thus store the groups as well. WDYT? +1 for the approach. However, SM will need to get the Group information to validate the Composite Application definition, parse it, etc. Therefore, we will need to make the relevant information available to SM (and any other interested party) via a service call. -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com<http://wso2.com/> lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 -- Thanks and Regards, Isuru H. +94 716 358 048
