Sitemap
Patterns
Recommended approaches to solving common issues
- Monitoring-as-code (MaC)
- Selecting a deployment strategy
- Immutable artefacts
- Make small changes
- Securing application logging
- Catch defects early (shift quality left)
- Using generative AI
- Reducing Code Complexity
- Write effective documentation
- Code reviews
- Docs as code
- Observability by OpenTelemetry
- Threat modelling
Principles
To guide the behaviour and decisions of engineering teams
- Design for success
- Be collaborative
- Work in the open
- Well managed code
- Write maintainable, reusable and evolutionary code
- Provide a good engineering experience
- Monitor and measure proactively
- Design from evidence
- End to end product ownership
- Deploy little and often
- Keep it simple
- Continuously maintain and evolve
- Quality assurance and testing
- Secure by design
- Zero trust
- Proportionate security
- Security is everyone’s responsibility
Standards
Explicitly stated expectations for engineering teams
- Infrastructure as code
- Writing a standard
- Managing secrets
- Encrypting data at rest and in transit
- Managing the security of software dependencies
- Infrastructure utilisation monitoring
- Low code workflow naming
- Developer Testing
- Minimal documentation set for a product
- Service reliability
- Designing and Maintaining an API
- Signing code commits
- Writing a principle
- Documenting an API
- Accessibility
- Open source licensing
- Test pyramid
About
Find out more about what we are doing