Swerve

Get started Read the manual

Why Swerve#

• Connections that stay open. Server-Sent Events, WebSocket and long polling from an ordinary request handler, and publish/subscribe between workers — no separate Node or Go service.
• Boot once, serve forever. The framework, routes and connection pools build once per worker, which then serves thousands of requests and connections.
• Isolated requests. Each request runs in a Scope of its own, so request-scoped state stays separate even with thousands in flight.
• Frameworks, not a rewrite. One adapter per framework runs your existing application; some serve requests concurrently within a worker, some one at a time. Which adapters overlap requests.