Show HN: Custom Haskell handlers for Nginx(github.com)
github.com
Show HN: Custom Haskell handlers for Nginx
https://github.com/lyokha/nginx-haskell-module
17 comments
Aw nice; I think haskell-wasm uses FFI too https://www.tweag.io/blog/2018-09-12-asterius-ffi/
super cool to see an nginx version of it!
super cool to see an nginx version of it!
Nice article, thanks for sharing this!
One of the things I think Python got right was the establishing of a WSGI (and, much later, ASGI) protocol to demarcate application from the reality of networks. Does Haskell have an equivalent? (Is it a monad?)
I don’t know much about Python, but from searching up WSGI, this sounds quite similar to the Web Application Interface [https://hackage.haskell.org/package/wai].
Ah - yes. Looks exactly the same sort of thing!
This is not a gateway, but you can build gateways with this. The module provides a lower-level handlers that can be divided into 4 major groups:
- Synchronous tasks: enable a full-featured language in Nginx location handlers - Asynchronous tasks: Nginx worker's main thread do not block on waiting, fit very well IO-bound tasks - Asynchronous services: background tasks that are not bound to client requests - Content handlers: generate responses to client requests
Note that all of them run inside the Nginx worker process, synchronous - within the main worker's thead, asynchronous - in the lightweight threads of the Haskell runtime.
As to Monad and demarcation. The synchronous tasks are sub-divided into pure and impure tasks. Pure tasks are guaranteed in compile time to not launch missiles in run time. Impure tasks are wrapped inside the IO Monad and allowed to do whatever usual C code can do. Btw, guarantee of purity is not a virtue of Monad solely, but rather a more complex thing, e.g. hiding IO constructor does not let escape from IO. Besides IO, there are various effect systems in Haskell which let applying more constraints on the effects but they are not (yet?) used in this module.
- Synchronous tasks: enable a full-featured language in Nginx location handlers - Asynchronous tasks: Nginx worker's main thread do not block on waiting, fit very well IO-bound tasks - Asynchronous services: background tasks that are not bound to client requests - Content handlers: generate responses to client requests
Note that all of them run inside the Nginx worker process, synchronous - within the main worker's thead, asynchronous - in the lightweight threads of the Haskell runtime.
As to Monad and demarcation. The synchronous tasks are sub-divided into pure and impure tasks. Pure tasks are guaranteed in compile time to not launch missiles in run time. Impure tasks are wrapped inside the IO Monad and allowed to do whatever usual C code can do. Btw, guarantee of purity is not a virtue of Monad solely, but rather a more complex thing, e.g. hiding IO constructor does not let escape from IO. Besides IO, there are various effect systems in Haskell which let applying more constraints on the effects but they are not (yet?) used in this module.
Haskell has WAI, which is similar to WSGI:
https://www.snoyman.com/reveal/first-app-wai-warp
https://www.snoyman.com/reveal/first-app-wai-warp
I used to build web apps around nginx and this would have been very useful for me then. Still a cool and tidy looking project! I am trying to think of some practical project I could use to try this.
I use warp to serve my projects and configure nginx as a reverse proxy. There might be a bit of overhead with this setup, but I like how simple it is.
This module can be used to build smart reverse proxies, not only round-robin, or hash or app-names based. For example, you may want to lookup destinations in some distributed cache db and alike.
I used to wrap everything in Nginx, but `warp` can hold its own candle, with HTTP2 and stuff. One less piece to configure.
Lovely project, much more polish than I anticipated.
Are you using this in production? Any benchmarks?
Yes, more than 5 years in a few components (mostly as smart reverse proxies as I said in another comment). They are high-loaded entry points on the client front, with a few hundred thousands clients. But I cannot say details due to NDA, even where it's used.
I did not compare performance with other alternatives such as OpenResty. I tried, but Nginx is very immune to resist loading it well from home network :)
I did not compare performance with other alternatives such as OpenResty. I tried, but Nginx is very immune to resist loading it well from home network :)
Nice, very nice!
[deleted]
Recently, I released version 3.2.0 with revamped README (with a lot of examples) and a new approach to building Haskell handlers using the modernized cabal v2-build for dependencies.