All my business servers are fronted by Nginx. I can't thank you enough Igor for such immense contribution to developers.
Do svidaniya, Igor, and thank you for Nginx
131–140 of 366 posts
Re: Do svidaniya, Igor, and thank you for Nginx
#132unrelated but ive always thought the F5 acquisition of NGINX made little sense. I think F5 saw the writing on the wall a little late, panicked, and bought the first competitor they could come up with that showed up in a Gartner quadrant. so much of the NGINX product that aligns with F5 as a competitive element is essentially already implemented and free by people who are already completely competent in load balancing…
I will say that as someone who managed a leased hosting environment years ago, we dropped our expensive F5 device once it became clear we could do the same load balancing in Nginx for the cost of a virtual server. Even with a small support contract from Nginx it was way cheaper.
Re: Do svidaniya, Igor, and thank you for Nginx
#133I know this is massively off-topic (have a good well paid "retirement" Igor), but I assumed that it would be written as Dos Vidaniya instead of (the correct) Do svidanyia My Russian studies is limited to listening to Sean Connery in The Russia House, and I guess I took Dos from the latin languages. Odd.
It's worse than that, the first thing that I scanned in the article is if he is alive. A title like that without a pre-defined context more often, in my native Russian perception, could mean much worse that just leaving a company. I'm glad he's doing well, I really enjoy NGINX as a casual user. It is a great gift to people. Удачи (good luck) or всего хорошего (best wishes) would not trigger such a reaction to scan th…
It sounds the same to an american english speaker without knowing a word of Russian since we can infer context and use the same farewell structure for the deceased.
Re: Do svidaniya, Igor, and thank you for Nginx
#134I remember the days circa 2009 when the Nginx docs pages still had lots of Soviet-style graphics... those were the days :)
I'd love to see this if anyone has a screenshot from this era!
Maybe these graphics? https://web.archive.org/web/20090228234133/http://wiki.codem...
Re: Do svidaniya, Igor, and thank you for Nginx
#135It still surprises me that NGINX beat out Apache so quickly even though Apache had way more modules and was/is entirely free vs. NGINX which is more or less "open core" with some nice features requiring commercial licensing.
Nginx always worked better and didn’t need to be tuned like Apache until you got to really enormous scales which were rare while even a little load on apache would require tweaking settings and experimentation.
Re: Do svidaniya, Igor, and thank you for Nginx
#136It still surprises me that NGINX beat out Apache so quickly even though Apache had way more modules and was/is entirely free vs. NGINX which is more or less "open core" with some nice features requiring commercial licensing.
I don't know how surprising it is, considering ease of use and "just works" beats all other considerations every time. If it didn't, we'd still all be using Novell.
Re: Do svidaniya, Igor, and thank you for Nginx
#137Oh my gosh, I thought he passed away.
Same. An editorialised title may have been preferable, but I understand the rules here generally don't allow that.
Re: Do svidaniya, Igor, and thank you for Nginx
#138Earlier quoted context omitted.
I think some of the pressure to update products is irrational. Just because something is newer and better is not yet reason to upgrade. If Apache did everything they needed I can imagine a company to completely forgo investigating Nginx and this might have been cause of that kind of statement. Or maybe this was just a way to explain it to younger devs who could not understand "don't break it if it works". We don't kn…
Well I think you and I are saying the same thing. Don't chase the shiny new thing. That said, by that time Nginx was a proven performance upgrade over Apache 1.x and 2.x. Quantifying that value is tough but it certainly had value attached to it.
Whether there is any value depends heavily on your application.
If your Apache is responsible for 0.1% of your costs then this is at most what you can save, even if Nginx was magically zero cost (like zero to install, maintain, zero computing resources, zero outages, zero hiring, zero project risks, etc.)
From my experience, most projects have way more important problems to solve and better opportunities to pursue than chase those very small improvements. Frequently it does not matter if one is 10 or even 100 times faster than the other.
Re: Do svidaniya, Igor, and thank you for Nginx
#139Fun story time: a few years back I worked at a major EU "traditional" (non-FAANG) IT company, and they were using Apache for handling web traffic. Rumour was that nginx, being already a backbone of half of internet, was dismissed as "too new" :) (we're talking mid-2010s)
Waiting for everybody else to test the product before you migrate is perfectly common sense strategy. Especially if that product does not give you any special edge over competition.
I think the irony is that newness is irrelevant once it's being used at a certain scale. You can battle test more in an hour than you could a small scale project in ten years.