Details
-
Epic
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
-
DAM scalability
-
Empty show more show less
Description
Context
See the notes from UHZ for pain points and initial findings
Moving assets out of JCR will also help in keeping the repository lean resulting in e.g. better search performance
Questions for discovery
- What options could be used to offload (big) assets to an external service?
- Align with the DAM as a service (ENVII-54) initiative.
- What type of services would we support? (Mind the data privacy laws when it comes to cloud services like S3).
- Jackrabbit Oak's direct binary access feature allows directly accessing binaries through pre-signed URLs while only keeping handles in JCR for e.g. managing access control. It also supports CDNs. Could something along these lines be implemented for Magnolia?
- Room for Servlet IO optimization: non blocking IO?
Customer feedback
- Belimo reports slowness of the asset chooser when listing assets and when selecting an asset: asset chooser slow to display assets.MP4

Checklists
Acceptance criteria
Attachments
Issue Links
- links to