Platform / Distributed Systems Engineer

Complex systems. Boring on purpose.

Hello, I'm Davidson! I build backend and platform systems that stay understandable when they fail. My work centers on explicit state, recovery, observability, and dependable production operations.

You can see some of those projects here, read my blog, or learn more about me. Feel free to contact me if you have any questions about my work.

Portrait of Davidson Ekpokpobe

Selected projects

In development / control-plane design

Branchplane

Early design work for an ephemeral environment control plane.

Branchplane is still at the system-model stage. I am using it to work through control-plane failure modes around desired state, reconciliation, cleanup, and one-shot deployment workflows.

  • Reconciliation
  • Idempotency
  • Leases
  • Failure recovery

Production software and migration

Standard Schools

Academic operations software for two campuses and more than 2,000 students and staff.

A production rewrite that preserved populated data, kept rollback possible, and separated permanent student identity from academic-session enrolment.

  • Next.js
  • PostgreSQL
  • Prisma
  • Tenant isolation

Realtime product engineering

theSwiftLine

A real-time queue product for waiting somewhere else.

Queue position is changing state, not a page to refresh. The system combines durable queue records with live updates, push notifications, reconnect-aware clients, and a server-fetch fallback.

  • .NET
  • SignalR
  • PostgreSQL
  • PWA

Production engineering

How I build

Production systems have to survive contact with reality. My work spans backend systems, cloud infrastructure, security, reliability, and the operations around them.

01

Data that keeps moving

PostgreSQL CDC with Debezium and ClickHouse, plus asynchronous workflows over Azure Service Bus.

02

Disposable environments

PR-scoped Azure infrastructure with Pulumi and CI/CD, backed by explicit lifecycle and recovery thinking.

03

Systems you can inspect

OpenTelemetry with Prometheus, Loki, Grafana, and Tempo, alongside synthetic monitoring and security remediation.

Current direction

Building infrastructure that remains understandable when it fails.

I am moving deeper into platform engineering and the infrastructure required by AI and agent systems, without treating reliability as somebody else's layer.