Architecture Decision Records
This is a record of architectural decisions made by the Data Platform Team
To understand why we are recording decisions and how we are doing it, please see ADR-000
| ADR no. | Status | Title |
|---|---|---|
| ADR-000 | ✅ | Record Architecture Decisions |
| ADR-001 | ✅ | Use Cloud Platform for hosting infrastructure |
| ADR-002 | ✅ | Use Modernisation Platform for hosting infrastructure unsuitable for Cloud Platform |
| ADR-003 | ✅ | Use EntraID (formally AzureAD) for Identity and Access Management |
| ADR-004 | ✅ | Data should be pushed into Data Products |
| ADR-005 | ✅ | Use AWS Secrets Manager for Secrets |
| ADR-006 | ✅ | Use GOV.UK Eleventy Plugin for user documentation and front door |
| ADR-007 | ✅ | Use AWS Quicksight for data visualisation |
| ADR-008 | 🤔 | AWS Bedrock |
| ADR-009 | 🤔 | Use AWS SageMaker for analytical tooling |
| ADR-010 | 🤔 | Documentation |
| ADR-011 | 🤔 | Use separate AWS accounts for data domains and products |
| ADR-012 | ✅ | We will host DataHub internally |
Statuses:
- 🤔 Proposed
- ✅ Accepted
- ❌ Rejected
- ⌛️ Superseded
- ♻️ Amended
This page was last reviewed on 17 August 2023.
It needs to be reviewed again on 17 February 2024
by the page owner #data-platform-notifications
.
This page was set to be reviewed before 17 February 2024
by the page owner #data-platform-notifications.
This might mean the content is out of date.