Skip to content
Kedgeworks
← All workPlatform2021–22Team · Scale

Building the team and stabilising the pipeline.

20m+customers served
12stateless Node services maintained
The situation

GoDaddy needed a new team built around a set of stateless Node.js microservices supporting a customer base of more than twenty million. The deployment pipelines those services shipped through were not stable enough to grow on.

The constraint

Growing a team and fixing the pipeline are the same problem. Every new engineer arriving into an unreliable deploy makes the deploy more unreliable, so the working practices had to change at the same rate as the headcount.

What we did

We helped build the engineering team from scratch and maintained roughly twelve stateless Node services, a functional codebase using RamdaJS, Fluture and Flow, organised around domain-driven design.

In parallel, he stabilised the deployment pipelines on Jenkins and Kubernetes/OpenShift and introduced new working practices, so the growing team inherited a process rather than a habit.

The outcome

A working engineering team, twelve services under maintenance for a customer base over twenty million, and deployment pipelines that could carry the growth.

Stack
  • Node.js
  • RamdaJS
  • Fluture
  • Flow
  • Domain-Driven Design
  • Kubernetes
  • OpenShift
  • Jenkins
  • Kibana
Related

Working on something similar?