Context

See the notes from UHZ for pain points and initial findings

Removing old tasks created by publishing will also help in keeping the repository lean resulting in e.g. better search performance. See SUPPORT-6301.

Customer feedback

From the product board (1, 2):

• Belimo: "Sub-nodes are never-ending due to the amount of content. 40k pages 
  Mgnl can handle the content but lagging (GWS-1310, this is Arvato's ref.no.) becomes a problem when there are embargoed publication needs:
  IR section - Semi & Annual report - Push all Master changes simultaneously. We tried to break them up into groups and break down publications, but it still takes some time: the status bar of progress gets stuck"
• Argos/Habitat/Sainsburys: "The author's instance publishing slows down when a too number of tasks are happening at the same time"
• Argos/Habitat/Sainsburys: "Sync module (with some customisation) to populate new publics with content. Takes up to 1 hours to sync content (currently runs sequential but looking to move to parallel to speed up process)
• Argos/Habitat/Sainsburys: "Publishing workflow speed"
• Belimo, Pooja Bhavsar: "Sub-nodes are never-ending due to the amount of content. 40k pages 
  Mgnl can handle the content but lagging (GWS-1310, this is Arvato's ref.no.) becomes a problem when there are embargoed publication needs:
  IR section - Semi & Annual report - Push all Master changes simultaneously. We tried to break them up into groups and break down publications, but it still takes some time: the status bar of progress gets stuck"

Questions for discovery

Publishing content in Magnolia is currently transactional: on publication all public instances will update to the new content, only then will the author instance show the content as published.

• How could we implement non transactional publishing?
• What consistency guarantees could we provide? What use cases would those cover? Which not?
• Could we use a git based solution (see also MAGNOLIA-9052)?
• Can we offload publishing to a queuing solution?
• How would external solutions (git, queue) affect overall complexity? See also this customer comment.
• How should we reflect the state of content in the author UI for these cases?

Customer feedback

• Belimo reports slow publishing (deleting 10 pages takes about 50 seconds): publishing 10 deletions is slow (50 seconds).MP4