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
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
