Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-9055

Improve DAM scalability

    XMLWordPrintable

Details

    • Epic
    • Resolution: Unresolved
    • Neutral
    • None
    • None
    • None
    • DAM scalability

    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

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                mduerig Michael Duerig
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated: