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
