Hi all, We need to come up with a proper design for this problem. We are not just talking about 4 AppServers here. We are talking about 4 stratos-live deployments and AF. As a workaround we are going to switch off caching in all App Servers but this is not the ideal solution. Is it practical to have the same cache shared among all clusters, which is a good quesiton. The ideal solution is to have a API that we can call in each cloud to say that resource got updated and AF controller can call it. WDYT?
thanks, dimuthu On Wed, Jun 26, 2013 at 3:38 PM, Dimuthu Leelarathne <[email protected]>wrote: > Hi all, > > This has a delay of 15 minutes. The values won't be updated for 15 > minutes. Is there a solution for this? > > thanks, > dimuthu > > > On Mon, Jun 3, 2013 at 10:31 AM, Senaka Fernando <[email protected]> wrote: > >> Hi Ajanthan, >> >> We need a better name than "dependencies", but apart from that this looks >> good. >> >> Thanks, >> Senaka. >> >> >> On Sat, Jun 1, 2013 at 11:07 PM, Ajanthan Balachandran <[email protected] >> > wrote: >> >>> Hi All, >>> >>> In App Factory, users can create resources through configure UI,put >>> different values for each stages(dev,qa...etc) and access those resources >>> in their applications through registry api.We achieved this through >>> registry mounting. >>> >>> App Factory /_system/governance is mounted to common DB.The governance >>> registry of App Factory will looks like follow >>> >>> /_system/governance >>> |-dependencies >>> -|dev >>> |-foo(dev value) >>> -|qa >>> |-foo(qa value) >>> -|stging >>> |-foo(staging value) >>> -|prod >>> |-foo(prod value) >>> >>> The governance registry of the dev app server also will be mounted to >>> the same common DB.In addition to that /_system/governance/dependencies >>> of the dev appserver also will be mounted to >>> /_system/governance/dependencies/dev of common DB. >>> Same mounting model will be set to all the app servers in other stages >>> as well. >>> >>> Then programming model for accessing this resource will looks like >>> follow. >>> >>> CarbonContext cCtx = CarbonContext.getCurrentContext(); >>> Registry registry = (Registry) >>> cCtx.getRegistry(RegistryType.SYSTEM_GOVERNANCE); >>> Resource resource = registry.get("dependencies/foo"); >>> >>> API Manager authorization token(API manager key) also will be managed as >>> above. >>> >>> WDYT? >>> -- >>> ajanthan >>> -- >>> Ajanthan Balachandiran >>> Senior Software Engineer; >>> Solutions Technologies Team ;WSO2, Inc.; http://wso2.com/ >>> >>> email: ajanthan <http://goog_595075977>@wso2.com; cell: +94775581497 >>> blog: http://bkayts.blogspot.com/ >>> >>> Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Senaka Fernando* >> Member - Integration Technologies Management Committee; >> Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> * >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> 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 > -- 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
