Next Build Persistent Server system diagram

[mreed101]

Description

The future of Next Build is to get content quicker to the user by being able to quickly create pages in a fashion similar to ISR instead of the current SSG implementation. This work first requires that all content is migrated over to next build and then content can be served faster instead of single daily builds. For this ticker we want to create a comprehensive overview of the system architecture for the Next Build persistent server. Diagram should include Software, Data Flow and Security Controls.

Acceptance Criteria

• Completed system diagram
• team agreement
• Approval from Platform
• Approval from Security

Notes

There is already a persistent server that is used for previews. We may be able to simulate it's setup.

[timcosgrove]

• Find examples of other architecture documentation that Platform has proceeded from
• Should we construct this as ideal, or as what TRM lists as approved

[jcbolling]

[laflannery]

@gracekretschmer-metrostar I'm not sure if you need this for the on demand publishing work? If not I would maybe recommend closing it