[MAGNOLIA-9055] Improve DAM scalability Created: 10/Aug/23  Updated: 07/Dec/23

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Epic Priority: Neutral
Reporter: Michael Duerig Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: dx-core-6.3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File asset chooser slow to display assets.MP4    
Issue Links:
Relates
Template:
Epic Name: DAM scalability
Acceptance criteria:
Empty

 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?
  • 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


Generated at Mon Feb 12 04:38:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.