Servers

Rakiba supports multiple Ring-compatible HTTP servers. All servers are swappable via configuration, allowing you to choose the best fit for your performance and feature requirements.

Server Options

Configure your server in rakiba.edn:

{:server :jetty}  ; or :undertow, :http-kit, :aleph, :immutant

Choosing a Server

Use this guide to select the right server for your needs:

• Default choice: :jetty - Mature, well-documented, excellent tooling support
• WebSockets: :http-kit - Native WebSocket support with minimal overhead
• High throughput: :http-kit or :undertow - Both handle 400k+ req/s
• Low latency: :http-kit - Sub-millisecond p99 latency
• Async/reactive: :aleph - Manifold-based, ideal for streaming
• Enterprise/WildFly: :immutant - When you need JBoss integration

Benchmark Results

All benchmarks were conducted to measure real-world performance across different middleware configurations.

Test Environment

Throughput

Latency (p99)

Key Findings

• http-kit has highest throughput (533k req/s) and negligible middleware overhead (<1%)
• Reitit routing cost is minimal - adds virtually no overhead vs basic middleware
• All servers handle 380k+ req/s with full middleware stack
• Latency remains sub-millisecond for http-kit across all tiers

Benchmark Methodology

Benchmarks measure performance across three tiers to isolate server overhead from middleware and routing costs:

Run your own benchmarks:

bb bench my-app jetty
bb bench my-app undertow
bb bench my-app http-kit

Next Steps

• Configuration - Full configuration options
• Deployment - Deploy to VPS or local sandbox
• Logging - Configure structured logging