Live data from Hacker News

Nginx Unit

nginx.com

211–220 of 236 posts

Re: Nginx Unit

#211

I hate sites like this. Im probably stupid but I have no idea what precisely it is after reading that page. I just know that marketing team wants me to believe it's going to be my saviour.

I can't say more than: Mee too!

Re: Nginx Unit

#212

Earlier quoted context omitted.

Wait, zeromq lost momentum ? When did that happen ?

Unfortunately, the founder of ZeroMQ, Pieter Hintjens passed away (due to cancer) [1]. He was a regular on HN [2]. ZeroMQ still works great and the open source community is still maintaining it on GitHub [3]. I just think people are also looking at other technologies. A lot of interest popped up in things like Apache Kafka and Samsa. I still think ZeroMQ holds a unique place due to its lightweight and simple nature.…

Yes, I am aware that Peter had passed away. I thought that it was implied that the project is not maintained anymore, which is not true.

Re: Nginx Unit

#213

Earlier quoted context omitted.

Wait, zeromq lost momentum ? When did that happen ?

When the main developer decided that it wasn't good enough and started working on nanomsg ( http://nanomsg.org/ )

zeromq is still very much in wide use. nanomsg doesn't have nearly as much documentation and community support as zeromq does.

Re: Nginx Unit

#214
post #130
post #27

> It is not recommended to expose unsecure Unit API why do people always use "not recommended" when they actually mean "do not ever do this or you'll end up the laughing stock in the tech press" Exposing this otherwise awesome API to the public will amount to a free RCE for everybody. So not ever expose this to the public, not even behind some authentication. It's very cool that by design it's only listening on a dom…

Technically, you can expose the Unit API within an internal network.

Why that still might not be a good idea: https://research.google.com/pubs/pub43231.html

Re: Nginx Unit

#215

Earlier quoted context omitted.

Do you not allow \n inside your JSON or encode your JSON as base64? If not you might have problems with disambiguating frame ends from line breaks inside frames. A common way for framing is to prepend each frame with it's encoded length. That's easier, faster and less error-prone than searching for ASCII delimeters.

a newline is encoded as the two characters "\n" in json and would not be confused with a literal \n (aka \x0a) character

Erm...JSON allows whitespace last I checked. \n (ie the actual \x0a) is a whitespace character, and so can appear as a discarded token in JSON. So you would basically have to restrict to a subset of JSON -- it's not actually JSON anymore at that point.

Re: Nginx Unit

#216
post #179

Earlier quoted context omitted.

Because people have a hard time figuring out what it is. Could you explain what it is? What benefits does it have to make it worth exploring? To me it looks like a rather invasive but flexible and dynamically configurable inetd. But it forces you to use its own libraries to receive http requests.

It's a lot like OpenResty ( https://openresty.org/en/ ), which is Nginx with a Lua interpreter embedded and bridged to its request-response cycle (the OpenResty page explains the point of that pretty well); but instead of Lua, Unit has a bunch of other language runtimes embedded.

Why remove Lua, though? I'm a heavy Lua user, which is why I use the openresty bundle of nginx. There's no reason for me to try this out. This is unfortunate!

Re: Nginx Unit

#217

Earlier quoted context omitted.

You can definitely do microservices that way but in reality they tend to be more granular both functionality wise and density-wise. With old skool SOA you'd typically have a monolith app with a bunch of endpoints. With microservices, especially in a containerized environment they tend to be more lightweight.

Microservices is just SOA rebranded for the cool kids. The fact that modern orchestration and tooling makes it easier to have more granular services changes the equation for how you factor the services, to be sure, but it's an evolution not a revolution.

This.

Re: Nginx Unit

#218

Earlier quoted context omitted.

Wait, zeromq lost momentum ? When did that happen ?

Dunno, I spent close to a week trying to get it to compile with and without encryption on Windows to no avail. Ended up using a Linux container on Docker to get the thing working.

That is troubling. I always thought of zeromq as having as good Windows support as anything not written exclusively for Windows.

Re: Nginx Unit

#220

Earlier quoted context omitted.

Wait, zeromq lost momentum ? When did that happen ?

Unfortunately, the founder of ZeroMQ, Pieter Hintjens passed away (due to cancer) [1]. He was a regular on HN [2]. ZeroMQ still works great and the open source community is still maintaining it on GitHub [3]. I just think people are also looking at other technologies. A lot of interest popped up in things like Apache Kafka and Samsa. I still think ZeroMQ holds a unique place due to its lightweight and simple nature.…

I have been curious how the community would hold up after Pieter's death. This project is a unique case because of how much work went into building community and welcoming contributions. That said, the world is a different place than in zeromq's heyday. Other commenters refer to Martin leaving the project, C++ regret, and a poor fit with node.js. Maybe in the face of all those changes zeromq's mature community is primarily why it lives as a project.
Post reply on HN