Infrastructure & DevOps

Infrastructure & DevOps

We're actively working on this page.

Scope

This section covers the platforms, tools, and practices we use to build, deploy, and operate our software. It includes our standards for containerization, continuous integration (CI/CD), and our primary cloud infrastructure services.

Overview

ADOPT

Proven technologies we have high confidence in; our default choices.


Docker

AWS (Amazon Web Services)

Jenkins

TRIAL

Promising technologies to explore and evaluate for adoption.


GitHub Actions

Docker Swarm

ASSESS

Interesting technologies requiring investigation.


 

HOLD

Not recommended for new work; plan migration from existing uses.


Manual Deployments

Technologies Breakdown

Docker ADOPT

Docker is our company-wide standard for containerizing applications. It provides a consistent, portable, and isolated environment, which is fundamental to our deployment strategy on AWS.


AWS (Amazon Web Services) ADOPT

AWS is our primary and strategic cloud provider. Our deep in-house expertise, certified engineers, and existing infrastructure make it the default platform for hosting all our applications and services.


Jenkins ADOPT

Jenkins is our established and primary tool for Continuous Integration and Continuous Delivery (CI/CD). It is the standard for automating builds, tests, and deployments for our core projects.


GitHub Actions TRIAL

We are actively trialing GitHub Actions on smaller projects as a modern, repository-native CI/CD solution. Its tight integration with our source code management simplifies build and deployment pipelines, especially for new or less complex services.


Docker Swarm TRIAL

Docker Swarm is being successfully used for container orchestration on a large-scale project. We consider it a proven, lightweight solution for managing multi-container applications that require orchestration without the full complexity of Kubernetes.


Manual Deployments HOLD

Manual and custom-scripted deployments are error-prone and lack the repeatability of automated pipelines. This practice is on hold; all projects are strongly encouraged to migrate to a standardized CI/CD tool like Jenkins for automated deployments.