NGINX Open Source: Reflecting Back and Looking Ahead
11–20 of 42 posts
Re: NGINX Open Source: Reflecting Back and Looking Ahead
#12Nginx Plus seems like they took a lot of the obvious feature upgrades, some which look fairly easy (remove cached item) and put them in a pay wall. Nothing wrong with that, just feels weird. And the pricing is enough to pay for a Windows license, not that IIS is even close to nginx (it's reverse proxy capability is terrible). I'm sad to hear about JS; I thought the work with Lua was going well and would be a better c…
Lua is a great scripting language in its own right, but the trouble is it's not JavaScript which at this time has an extraordinary amount of momentum behind it. You can use JavaScript inside Postgres, for example, which makes it extremely versatile as a glue language for back-end services. Lua has nowhere near the traction or support. Is there a C++ to Lua compiler that produces performant code when using an asm.js-l…
Re: NGINX Open Source: Reflecting Back and Looking Ahead
#13Nginx Plus seems like they took a lot of the obvious feature upgrades, some which look fairly easy (remove cached item) and put them in a pay wall. Nothing wrong with that, just feels weird. And the pricing is enough to pay for a Windows license, not that IIS is even close to nginx (it's reverse proxy capability is terrible). I'm sad to hear about JS; I thought the work with Lua was going well and would be a better c…
> I thought the work with Lua was going well The lua support is GREAT, and make a lot of complex stuff (standard outside authentication on multiple apps) simple as using a 20 lines lua script. Let's hope LUA doesn't fall to second class citizen.
Re: NGINX Open Source: Reflecting Back and Looking Ahead
#14Re: NGINX Open Source: Reflecting Back and Looking Ahead
#15It's annoying that they took SPDY support out of Community and put it into Plus. Want updates? Too bad, you gotta recompile.
Re: NGINX Open Source: Reflecting Back and Looking Ahead
#16Nginx Plus seems like they took a lot of the obvious feature upgrades, some which look fairly easy (remove cached item) and put them in a pay wall. Nothing wrong with that, just feels weird. And the pricing is enough to pay for a Windows license, not that IIS is even close to nginx (it's reverse proxy capability is terrible). I'm sad to hear about JS; I thought the work with Lua was going well and would be a better c…
I had a chat during an interview with folks from the Nginx team recently and definitely got the impression they are putting a lot more thought into the separation of Plus than this. One of the key features is the ability to add/remove backends at runtime, as well as, IIRC, some failover capability that makes Nginx Plus a potential competitor for things like F5.
Disclaimer: I am not associated with Nginx, except that I shook some folks hands, and I might have remembered something wrong. They went out of their way to illustrate to me, and I think they did, that Nginx Plus is more than just 'open core'.
If you read the prior article, linked in this one, the original author of Nginx is allowed to expound on this himself. An experienced Ops team can assemble a number of open-source components and custom code to accomplish some of the more advanced functionality in Nginx Plus, but I think it's saving more than a couple hours of customization. :)
Re: NGINX Open Source: Reflecting Back and Looking Ahead
#17td;rd: interesting things will move to the premium version, JS VM to power future versions, pluggable module API coming
Nginx Plus is a platform, not just a special version of Nginx open-source, where Nginx is a core component.
Re: NGINX Open Source: Reflecting Back and Looking Ahead
#18It's annoying that they took SPDY support out of Community and put it into Plus. Want updates? Too bad, you gotta recompile.
Re: NGINX Open Source: Reflecting Back and Looking Ahead
#19Re: NGINX Open Source: Reflecting Back and Looking Ahead
#20The question that you should always ask before going down an proprietary-add-ons business model is, what are you going to do the day someone develops the same functionality for the open source product, in a fundamentally different way? Are you going to rip out those parts every time you release your proprietary version? Because your customers are paying for those parts to be very stable.