Question 1

How do I set up WebSockets with http-kit?

Accepted Answer

http-kit provides built-in WebSocket support through its unified API—you can define handlers similar to HTTP routes. Check the wiki for examples on managing connections and handling real-time data efficiently.

Question 2

http-kit vs Jetty: which is better for Clojure?

Accepted Answer

http-kit is lighter and faster for high-concurrency scenarios with zero dependencies, while Jetty is more feature-rich and battle-tested. Choose http-kit for performance and minimalism, but Jetty if you need broader protocol support or enterprise features.

Question 3

Does http-kit handle HTTPS directly?

Accepted Answer

Yes, http-kit can configure HTTPS, but the README recommends using a reverse proxy like nginx for SSL termination in production for better security and performance hardening.

Question 4

How to benchmark http-kit's performance?

Accepted Answer

http-kit includes an extensive benchmark suite that you can customize and run locally. Refer to the wiki's benchmarking section for setup instructions, metrics, and example results to compare against other servers.

Question 5

What are http-kit's memory requirements under load?

Accepted Answer

http-kit is designed for efficiency with O(n) RAM usage, using only a few kB per connection. Tests show it can serve over 600k concurrent connections with minimal memory, ideal for resource-constrained environments.

Question 6

Can I use http-kit with existing Ring middleware?

Accepted Answer

Yes, since http-kit is Ring-compliant, it works seamlessly with all standard Ring middleware. You can migrate from Jetty without changes to your middleware stack, as it's a drop-in replacement.

http-kit

What is http-kit?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions