██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╔════╝██╔═══██╗██╔══██╗██╔═══██╗██║ ██║ ██║ ██║██████╔╝██║ ██║██║ ██║ ██║ ██║██╔══██╗██║ ██║██║ ╚██████╗╚██████╔╝██████╔╝╚██████╔╝███████╗ ╚═════╝ ╚═════╝ ╚═════╝ ╚═════╝ ╚══════╝
Yes, really. A language designed in 1959 for payroll batch jobs on mainframes is answering your HTTP request, one fork()ed process per connection, dispatched by socat, inside a Docker container, built by Limelite Deploy's build host, pulled from ECR, fronted by nginx with a Let's Encrypt certificate.
Stack: GnuCOBOL → socat → Docker → ECR → EC2 → nginx → TLS
Health endpoint: /api/health
IDENTIFICATION DIVISION. PROGRAM-ID. REGRET-NOTHING.