How do we keep track of what data is in BAM vs what data comes form other sources?
I think it is a good idea to not replicate data, but the source of data need to be known all the time for help verify/test accuracy. Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Fri, Nov 8, 2013 at 2:54 PM, Gayan Dhanushka <[email protected]> wrote: > Hi All, > > There are some scenarios in appfactory where the data which needs to be > published to BAM is already captured by an underlying appfactory database > (e.g. issue tracker). Hence there is no need of publishing them again to > BAM and running a expensive hive query on top of it. But still there has to > be some Some observations are as follows. > > 1 ) Application creation and life cycle management details are captured in > the registry. But since registry resources are saved as a xml string, the > conversion of the xml to json is required in the jaggery datafile. > 2 ) Issue tracker has a underlying mysql database. Hence data can be > directly pulled from the issue tracker database. > 3 ) Builds and commits data needs to be published to BAM anyway since they > are not captured by the appfactory databases. > > Is it good to read data directly from the registry databases? Will it > cause degradation in performance of the appfactory? Is it ok to change the > architecture and use underlying appfactory databases whenever possible? > WDYT? > > Thanks > GayanD. > > Gayan Dhanuska > Software Engineer > http://wso2.com/ > Lean Enterprise Middleware > > Mobile > 071 666 2327 > > Office > Tel : 94 11 214 5345 > Fax : 94 11 214 5300 > > Twitter : https://twitter.com/gayanlggd > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
