schema_version: 1 model: id: team-wiki name: Team Wiki description: > An arc42 example: a small self-hosted wiki for an engineering team. Sections 1 goals, 2 constraints, 3 business context, 10 quality, 11 risks and 12 glossary are on this overview; 0300-context holds 3 technical context, 0500-building-blocks 5 building blocks, 0600-runtime 6 runtime, 0700-deployment 7 deployment and decisions 9 architecture decisions. diagram_type: architecture meta: title: Team Wiki - business context output: main.html decisions: [sso-only-via-company-idp] components: - ref: engineer pos: [40, 60] size: [130, 60] - ref: wiki-admin pos: [40, 260] size: [130, 60] - ref: wiki pos: [280, 160] size: [150, 60] - ref: idp pos: [520, 60] size: [150, 60] - ref: object-store pos: [520, 260] size: [150, 60] connections: - { from: engineer, to: wiki, label: reads, variant: emphasis } - { from: wiki-admin, to: wiki, label: runs } - { from: wiki, to: idp, label: sign-in, variant: security } - { from: wiki, to: object-store, label: files } cards: - dot: cyan title: 1 Quality goals items: - Findability - any page found in two searches - Security - only current staff can read - Operability - one person runs it in an hour a week - dot: slate title: 2 Constraints items: - Runs on the company Kubernetes cluster - Sign-in only via the company identity provider - dot: emerald title: 10 Quality scenarios items: - A search over 5000 pages answers in under 1 s - A leaver loses access within 5 minutes - The admin restores last night's state in 30 minutes - dot: rose title: 11 Risks items: - Identity provider outage blocks all sign-ins - Backups untested until a restore drill is run - dot: violet title: 12 Glossary items: - Space - pages of one team, mapped to a group - Revision - one saved version of a page - Attachment - a file stored beside a page