Adopt - The default choice when selecting technologies
Assess - Technologies that we believe may be valuable, and are currently being assessed to understand their value and impact.
Hold - Technologies in hold must no longer be used for new development
Cloud compute gives us the flexibility of scaling to demand. Our initial migration was a very similar set up to what we had previously. We will continue to look at improving this to gain the full benefits.
Mature build and deployment tooling
We are seeing benefits of using on-demand testing environments for quick and reliable acceptance testing.
For static storage.
CDN to go in front of S3 etc.
These tools could help us to reduce environment-specific issues, and improve documentation. We have picked terraform as it is the best supported cross platform tool. Although parts of scripts would need to be rewritten, it provides a consistent base across platforms (rather than using cloudformation etc)
We need to understand the potential that server-less platforms can offer in reducing operational overhead of server management with a small operations team. Currently testing in MAS. For simple logic, can be sensible. If it is complicated, just use a sever. Part of the assessment will be defining when it is and isn’t sensible to use.
As part of this we are trialling API gateway.
Currently looking at what capabilities this can provide us
On a project by project basis we will assess if things should be self hosted.
We’ve not seen enough benefits in running docker in production over our existing Teamcity -> Octopus deploy -> AWS EC2 infrastructure.