FeathersJS v5 ESM Transition for Low-Traffic Resource Optimization

Reducing infrastructure costs for low-traffic workloads often involves minimizing memory overhead and improving startup efficiency. FeathersJS v5 (Dove) introduces a shift toward native ESM, which potentially enhances tree-shaking and runtime performance compared to the CommonJS patterns used in v4.

When optimizing for minimal resource footprints, the choice between Express and Koa adapters remains a key configuration decision. While both are supported, the memory profile and initialization speed may differ when deploying to constrained environments or serverless platforms where idle costs are a priority.

Given the architectural shift in v5, what are the specific memory usage trade-offs between the Koa and Express adapters for a minimal service set? Does the native ESM implementation in v5 provide a measurable reduction in baseline heap usage for low-traffic applications?