Skip to content
Snippets Groups Projects

Refactor the backend to make it scale better

    • Open Issue created by David Douard @douardda

    See https://hedgedoc.softwareheritage.org/RJQjBSR2TmuVzD6NRFFCeg?both

    Migrated from T3453 (view on Phabricator)

    Designs

      Child items 0

      2. No child items are currently assigned. Use child items to break down this issue into smaller parts.

      Activity

      • David Douard added Provenance database priority:High labels

        added Provenance database priority:High labels

      • David Douard
        David Douard @douardda ·
        Author Maintainer

        I've been thinking a bit about the refactoring of the ProvenanceStorageServer as described in the doc, with a series of queues between the public API and the backend database.

        And it's unclear to me how this can be done efficiently. The

        splitting the actual db operations into several queues/writers (by id range, for each entity)

        is unclear to me. Does it mean there one queue for each entity type? (revision, content, directory) and each relation type? (content_in_revision, etc.) I don't get the split per id range.

      Please register or sign in to reply