LoomProxy is a next-generation, lightweight API Gateway designed to handle massive concurrency without the "Reactive Complexity". It leverages Java 21 Virtual Threads (Project Loom) for scalability and Panama FFI for zero-copy Linux syscalls.
Historically, developers had to choose between two compromises:
- Simplicity (Zuul 1 / Servlet): Easy to write and debug, but crashes under load because OS threads are heavy (~1MB per request).
- Performance (Spring Cloud Gateway / Netty): Highly scalable, but uses a reactive model that leads to "Callback Hell" and impossible-to-read stack traces.
LoomProxy kills this trade-off. We use Virtual Threads: your code stays simple (Blocking), while your scalability becomes infinite (Async).
We don't just claim performance; we measure it. Using our internal ScalabilityBenchmark, we tested LoomProxy’s ability to manage high-density workloads on standard hardware.
Time to spawn and process 10,000 parallel tasks (Lower is better)
