DevOps and infrastructure

02 What I built

• 01

  Kubernetes move

  Led the move of the services and databases to Kubernetes over planned nights, with dry runs, rehearsals and rollback notes. A checksum of the rows on both sides proved the data was the same.

• 02

  Move generator

  Turned the old hosting setup into Kubernetes files, worked out which service needs which, and started them in the right order, with CPU and memory sized from real use.

• 03

  Infrastructure as code

  The whole platform is described in reviewed files, the cluster is kept in line with them automatically, and metrics, logs and alerts watch it.

• 04

  Shared CI/CD

  One reusable deploy workflow for all services, and a script writes the small file each repo needs from one list, so every service ships the same way.

• 05

  Database backups

  Backups kept for different lengths of time, with a weekly automatic test that really restores one.

• 06

  Event bus move

  A bridge and a plan to move service messages from Redis Streams to Kafka without losing or doubling any. The switch point is taken from the last delivered message, not from clocks. I wrote the full plan, and wrote down the trade-off when the company chose a single switch.

• 07

  Self-repair ops agent

  AI agents look into and fix incidents, but act only after repeated failures and only within set risk levels.

• 08

  AI coding workspace

  A control layer over all service repos so AI coding agents can safely change the whole system. Rules load only when needed, a generated map shows which service talks to which, and it adds safe read-only tools for production logs and databases.

03 How it works

1. 01The whole platform is described in reviewed code files.
2. 02The servers are kept in line with those files automatically.
3. 03Every service ships through one shared deploy workflow.
4. 04Metrics, logs and alerts watch the system.
5. 05A weekly automatic test really restores a database backup.