RuwanY, if we use a shared file system we can get rid of dep sync right ? Thanks Rushmin
Sent from my mobile. On Aug 4, 2015 4:50 PM, "Ruwan Yatawara" <[email protected]> wrote: > Approach 2 does seem the best way to go. > > But if we are going with this approach, since we will have to rely on > depsync there might at times be a delay of 15 seconds (sync thread interval > time) or more (time to checkout the artifacts from svn) in synchronizing > the artifacts. > > Thanks and Regards, > > Ruwan Yatawara > > Senior Software Engineer, > WSO2 Inc. > > email : [email protected] > mobile : +94 77 9110413 > blog : http://ruwansrants.blogspot.com/ > www: :http://wso2.com > > > On Tue, Aug 4, 2015 at 4:41 PM, Ruwan Abeykoon <[email protected]> wrote: > >> +1 *Approach 2*: File directory >> >> Since, >> 1. File system is faster than any of the database access methods >> available and can be made to serve content with almost zero CPU load. >> 2. In clustered environment, one can mount shared file system for better >> performance. >> e.g NFS(Free) or commercial products >> 3. Backup, restore is easy in shared file system. I think this >> is appealing for sys-admins. >> >> Cheers, >> Ruwan >> >> On Tue, Aug 4, 2015 at 4:16 PM, Sajith Ariyarathna <[email protected]> >> wrote: >> >>> Hi All, >>> >>> Images are uploaded as banners, screenshots and icons in the publisher >>> of AppM. Currently (in version 1.0.0) these images are stored in two >>> different manners. >>> >>> *In web apps* (02 images) >>> >>> Images are stored in the "JAGH2" database using the Jaggery Storage >>> Manager of ES v1. >>> >>> *In mobile apps* (05 images) >>> >>> Images are stored in a file directory (default location is >>> "<AppM_Home>/repository/resources/mobileapps/"). This directory is also >>> used to store uploaded mobile apps (.apk & .ipa files) and it is shared >>> between nodes in a clustered environment (see email thread [1] ). >>> >>> >>> We are hoping to use a single approach for both web apps and mobile apps >>> in the upcoming AppM release. Some comments/points regarding two approach >>> is given below. >>> >>> *Approach 1*: "JAGH2" database via Jaggery Storage Manager >>> >>> 1. In a clustered environment, user have to share the "JAGH2" database. >>> This might be an extra burden for the user. >>> >>> 2. There are some performance concern regarding the Jaggery Storage >>> Manager as it access the database using Jaggery. >>> 3. What is the status of the Jaggery Storage Manager in the ES v2.0 as >>> AppM will be moving to Es V2.0 in the future. >>> >>> *Approach 2*: File directory >>> >>> 1. Since majority of images (05) are stored in the directory, moving the >>> rest (02 images) will be easy. Developing a migration-tool (which copies >>> existing images in the DB to the directory) will be easy too. >>> >>> 2. We can improve the files/folder structure inside the directory >>> following manner. >>> >>> [image: Inline image 3] >>> >>> >>> Your feedback regarding this matter is highly appreciated. >>> Thanks. >>> >>> [1] [Dev] [AppM] Issue with clustering AppM with large mobile apps >>> >>> -- >>> Sajith Ariyarathna >>> Software Engineer; WSO2, Inc.; http://wso2.com/ >>> mobile: +94 77 6602284, +94 71 3951048 >>> >> >> >> >> -- >> >> *Ruwan Abeykoon* >> *Architect,* >> *WSO2, Inc. http://wso2.com <http://wso2.com/> * >> *lean.enterprise.middleware.* >> >> email: [email protected] >> phone:(+94) 777739736 >> > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
