Case studies
Eight case studies showing the operating context, the decision and the evidence behind the result. Pre-launch work is labelled.
8 of 8 case studies
Personal engineering work · public repository
Hierarchical OUs, a centralised security account, production-grade SCPs with root-account protection, and Security Lake telemetry in OCSF — provisioned end to end in Terraform.
Cross-account least-privilege IAM with S3 + DynamoDB + KMS remote state
a London-headquartered DeFi protocol · 2023–present
Rebuilding release engineering around ArgoCD and Helm so that rolling, blue-green and canary deploys became routine rather than events.
Median pipeline 35 → 20 minutes, measured as ArgoCD sync plus Helm rollout, 90-day medians either side
Zyntrix Technologies Limited · Wuse 2, Abuja · four clients
One delivery standard across nine runtimes — AWS, Azure, GCP, Vercel, Render, Railway, Heroku, App Engine and Azure App Service — chosen per client rather than by default.
A written platform-selection framework: operability after handover, compliance, cost at the client's scale, traffic shape, data residency
At Zyntrix Technologies Limited, for Celebrations Nigeria
Two production-grade systems around Odoo 19: event-driven Glovo inventory and order middleware for three stores, and a secure employee self-service portal spanning HR, payroll, attendance and multi-stage requests.
Encoded five inventory rules — including Glovo ≤ floor(Odoo / 2) — across initial sync, Glovo orders, walk-in POS sales, receipts, transfers, adjustments and returns for AA, AK and Lekki
Zenith Chain · Abuja · 2020–2021
Nodes, wallet services and indexers on Kubernetes across 20+ microservices, with event-driven autoscaling absorbing high-throughput transaction spikes without degrading response times, and reusable Terraform modules behind every environment.
99.99% uptime across blockchain nodes, wallet services and indexers — high-availability configuration and automated failover, on checks that measure consensus progress rather than process health
Personal engineering work · public repository
Prometheus, Grafana and Alertmanager for metrics, an EFK pipeline for logs and Jaeger for traces on one EKS cluster — with two instrumented Go services routing OTLP through an OpenTelemetry Collector rather than exporting to each backend directly.
One OTLP path per service instead of one exporter per backend: the Collector fans metrics out to Prometheus and traces to Jaeger, so swapping a backend is a Collector config change rather than a code change
Personal engineering work · public repository
An expense-tracking API delivered from source to Amazon EKS: a non-root Node.js container, MySQL on RDS, layered Terraform for the network and platform, and a Jenkins and Helm delivery path with SonarQube quality gates and Nexus artefact storage.
Separated compute and state across private EKS nodes and MySQL RDS database subnets, with public traffic terminating at an ACM-backed Application Load Balancer
At Zyntrix Technologies Limited, for Anchor Cooperative
Infrastructure, delivery pipeline, security posture and observability for a member-owned cooperative — a modular FastAPI monolith over PostgreSQL, packaged to move to EKS without a rewrite. Unrelated to the fintech of a similar name.
Transaction, ledger entries and the outbox event commit in one database transaction — a recorded payment cannot outlive a failed ledger write, and no event is lost when the queue is down