3 ms·

I was one of the first committers on Mongrel2 (actually, second behind Zed) and I still am (though mostly as a historical accident, I haven't contributed anythi

I was one of the first committers on Mongrel2 (actually, second behind Zed) and I still am (though mostly as a historical accident, I haven't contributed anything of substance since SSL). In my opinion, this is great. I think Mongrel2 is an excellent proof-of-concept, and if it provided the impetus for a much more widely used project like nginx to go down a similar path (though it's just a module right now), then everyone wins. That said, this certainly isn't in nginx mainline, and it's very feature poor as compared to Mongrel2. One could not simply swap in nginx with this module for an existing Mongrel2 installation.

igrigorik 15y ago
Alex, do you know if Mongrel2 have any interesting production deployments? In terms of visibility, throughput, or any other metrics. Outside from the architecture discussions, I haven't see any mentions of it.. (and I'm a fan of the architecture).
piotrSikora 15y ago
> it's very feature poor as compared to Mongrel2. One could not simply swap in nginx with this module for an existing Mongrel2 installation. That's because this is _transport_module_ and what Zed did with Mongrel2 is build a level 7 protocol on top of ZeroMQ messages. Even if this would support PUSH/PULL + PUB/SUB sockets right now, you would still need an _upstream_module_ that understands Mongrel2's level 7 protocol.
- piotrSikora 15y ago
  Head's up, I've started working on both: - PUSH/PULL + PUB/SUB support for ngx_zeromq (transport module), - ngx_mongrel2 (upstream module). Should be ready sometime next week.