Workstreams definition

This aims to explain and clarify the mission of the 2 workstreams defined inside the SRE domain.

Platform

We define the scope of this centre of expertise as all the systems we maintain and where we provide customization or where we take an off-the-shelf solution and add our own abstractions on top of it. The platform group is responsible for eliminating toil by working on automation at any level on infrastructure it manages. This group supports developers in using the platforms we maintain and help in optimising software delivery performance.

i.e: EKS, GHA runners, EC2 platforms…

Services & Observability

– services – We define the scope of this centre of expertise as maximising the reliability of software and services.

The workstream members are responsible for enhancing the visibility and performance of applications by optimising the use of managed tools.

This involves educating developers about the tool and working with them on finding the best solution for the applications.

– observability – The S&O workstream group ensures that we are able to measure performance, detect problems and eliminate failures.

The goal of observability is to understand what is happening across the whole infrastructure and among technologies, so issues can be detected and resolved to keep the systems efficient and reliable.

Also in charge of observability and building tools that help accomplish the mission.

Members of this workstream aim to proactively intervene to resolve any potential issue before it happens.

The management and providing metrics and information for the incident response is also part of its duties.

i.e: Github, Dynatrace, ELK… AWS Evangelisation Serverless Framework RDS/Elasticache Redshift CDN’s Github Artefact Storage 1/2 Cost Optimization, Incident Response, SIEM, DNS

We deliver our impact in four core pillars; Availability, Performance, Security and Cost.

Example Tools

The below venn diagram demonstrates some of the potential tools that could be included in each workstream. This list is not meant to be exhaustive or definitive, it’s more to help visualise how the two workstreams are complementary to one another.