Architectural Practices

Introduction

These pages give advice on the common approaches that we take across the Apprenticeship service. It will detail what approaches should be taken and why.

The approaches and patterns listed are expected to be followed but are not aimed at limiting new components, aspects or approaches. They are given to show the currently preferred approach within the service. Where a new approach or type of implementation is required for a project then it is perfectly acceptable that the approaches listed can be updated. If a new approach is to be taken by a project team then agreement and acceptance within the architecture group needs to be sought and agreed before any design is finalised (No implementation should be carried out without this).  

Our overall approach is driven from the GDS service design manual (service standard).

Some example of these are

• Iterate quickly
• Support incremental change

Also from the Technology Code of Practice

• Cloud first
• Open Standards

Supported Architecture Styles (sub-pages todo)

• Event Driven Architecture
• Micro-Services
• API Driven