I believe - we first thought of implementing a sort of Storage App that would perform this. Registry is used to store Meta-data -not Date by itself. IMO -storing binary data would become a performance bottleneck for the registry. I believe - we need to build a service (JAX-RS perhaps) that handles these aspects. The service can further expand to storing it on a database, storing it on disk or storing it on S3.
Since registry has implemented access management for assets -we can utilize that by having a pseudo structure in the registry. WDYT? Cheers~ On Wed, Aug 13, 2014 at 5:52 AM, Dakshika Jayathilaka <[email protected]> wrote: > Hi, > > IMO we need mechanism to store assets on external locations as wel. (ex: > dropbox, fileshare ) > most of the time users do not want to waste their bandwidth on > downloadable stuff. but in this case we need to implement verification > mechanism as wel. (SHA or MD5 hash for linked files) > > WDYT? > > Regards, > > *Dakshika Jayathilaka* > Software Engineer > WSO2, Inc. > lean.enterprise.middleware > 0771100911 > > > On Tue, Aug 12, 2014 at 5:53 PM, Sameera Medagammaddegedara < > [email protected]> wrote: > >> Hi Everyone, >> >> *Current State:* >> >> - All the resources of an asset are stored in a database(e.g. images >> and pdfs) >> - The embedded H2 database is used as the default data source >> - CRUD operations are performed using an intermediate layer that >> abstracts out the complexities of dealing with different database types >> - The business logic deals with an interface that uses get and put >> methods to access the storage layer >> - All resources are served from a single endpoint that is used to >> control access based on the state of the asset that owns the resource >> >> *Problems with the current implementation* >> >> - The need to test and support the storage implementation across >> databases other than H2 and MYSQL >> - The need to replicate tenancy within the database schema >> - The need to enforce access control logic in the endpoint used to >> serve the resources >> >> *Proposed Solution* >> >> - Store and serve the resources using the registry >> - *Advantages:* >> - There will not be any need to support multiple database types at >> the ES level >> - The use of registry roles to control access to the resources >> - *Open Questions:* >> - Is it prudent to serve content from the registry? >> >> >> Thank You, >> Sameera >> -- >> Sameera Medagammaddegedara >> Software Engineer >> >> Contact: >> Email: [email protected] >> Mobile: + 94 077 255 3005 >> >> _______________________________________________ >> 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 > > -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2 Inc Lean.Enterprise.Mobileware * ~Email [email protected] <[email protected]>* * ~Mobile +94712112165 <%2B94712112165>* * ~Website dulitha.me <http://dulitha.me>* * ~Twitter @dulitharw <https://twitter.com/dulitharw>* *~Github @dulichan <https://github.com/dulichan>* *~SO @chan <http://stackoverflow.com/users/813471/chan>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
