But can I use Perl 6?
Nginx Unit
221–230 of 236 posts
Re: Nginx Unit
#222I 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.
Re: Nginx Unit
#223I 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.
Re: Nginx Unit
#224This looks pretty cool, and makes me sad that Mongrel2 never became popular. In short: Mongrel2 solves the same problem, but does it by letting your application handle requests and websocket connections over ZeroMQ instead of eg FastCGI. I guess it lost momentum when ZeroMQ did. Anyone know why? Sounds like a dream solution in the current microservice hype. http://mongrel2.org/
microservices on their face seem cool, but in reality not so much. really, it's just SOA taken to an unnecessary extreme.
Re: Nginx Unit
#225I 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.
Yeah I had a hard time finding out what this site did.
> NGINX Unit is a new, lightweight, open source application server built to meet the demands of today’s dynamic and distributed applications.
That means everything and nothing. They wasted their intro sentence on it. They probably don't have a very good idea of what it is either.
Re: Nginx Unit
#226Amazing progress! Someone introduce them to CGI.
Re: Nginx Unit
#227Earlier quoted context omitted.
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
I did compliance work for a lot of start-ups and never came across a company that understood this concept. The majority thinks that their wireless router is already doing this via the Guest account.
Re: Nginx Unit
#228Earlier quoted context omitted.
I recently switched from zeromq to straight libuv sockets with jsonl (\n-separated json) payloads. Because I'm working inside a Node process, combining zmq's threading model with Node's threading model was a pain. Now, there's a single IO thread which is the same as the Javascript engine thread, and I can use uv_work to run CPU-intensive tasks on multiple cores.
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.
Re: Nginx Unit
#229Sounds like uWSGI based on the description. I wonder how it'll play along with certain environments like Kubernetes.
Re: Nginx Unit
#230I 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.
EDIT: https://github.com/nginx/unit/blob/master/README.md is the better reading.