2 years ago

Category: Business, Security, Redis, Terraform, Infrastructure, Architecture, encryption, gitlab, automation, yaml

This post explores evaluating the criteria for selecting each tool focusing on a balance between meeting functional and non-functional requirements, and maximizing value. Source code is potentially your most valuable asset, and so we start by choosing a source code management tool. These tools normally have high non-functional requirements in order to protect your assets and to ensure they are available to the organization when needed.

To support infrastructure as code best practices, Runners are deployed with Helm and are stored and versioned as Helm charts.

As a result, the primary non-functional requirements for your production container registry are likely to include high availability, durability, transparent scalability, and security.