Skip to content
Ever Code
Projects

National election management platform

A system whose entire year of traffic arrives on one fixed date.

The problem

Election day is not a load curve you can smooth out. The existing system was a monolith with no deployment story, and the one day it had to work was known years in advance and could not slip.

What I built

Rebuilt along module boundaries on Laravel Octane over Swoole, with Horizon handling queued work. Infrastructure is defined in CDK and runs on EKS, so environments are reproducible rather than hand-assembled. The platform was load tested against projected election-day concurrency well ahead of the date.

Where it landed

Capacity limits surfaced in load testing, where they are a configuration change, rather than on the one day that matters.

Tell me what is breaking.

Send a short description of the system and the problem. You get a technical answer, not a sales call.