161–170 of 190 posts
I am really surprised no one brought on the performance topic. Now I have been out of web programming for half a decade or more, but if my memory is not completely gone I remember that nginx was about an order of magnitude faster than apache under heavy load. Is it still the same nowadays?
Earlier quoted context omitted.
fpm is being dropped now that php 7 contains many of the improvements that made fpm popular. php_mod+apache with .htaccess turned off is the faster stack. Put a nginx server to server static content in front and that's the fastest stack going forward
FPM is being dropped? This is news to me, where can I read about this?
The below are links to benchmarks and discussions around mod_php vs. fpm. These are from last year 2016. Fast forward to today; I am seeing people move to php 7 and move back to mod_php. I believe we are at the start of a movement. Articles/stories will follow but only after the fact.
https://www.symfony.fi/entry/symfony-benchmarks-php-fpm-vs-p...
https://www.reddit.com/r/PHP/comments/4bi9a4/why_is_mod_php_...
This is kind of a weird statistic to try to analyze. So many uses of nginx are just the act of putting an Apache/IIS/etc site behind nginx, so technically, both servers still have market share but you only see nginx. It's just that nginx makes it so easy to do certain things, like supporting modern HTTPS, that you might as well add it to your stack rather than replace something.
As someone younger who never really used Apache, I don't see any reason to do anything with it instead of Nginx. Other than supporting "legacy" setups, whats the point of Nginx load balancing Apache? Configuring nginx is just so much more intuitive.
Earlier quoted context omitted.
PHP is definitely a huge chunk of the reason why nginx has taken over Apache. php-fpm with nginx is the defacto standard , and PHP is far more prevalent than a lot of people think. Apache's mod_php(X) vs. nginx+php-fpm isn't even a debate. If someone is currently using Apache+mod_php, they probably have a smaller product that will eventually have to switch to nginx+fpm in order to scale. While I imagine PHP is the si…
fpm is being dropped now that php 7 contains many of the improvements that made fpm popular. php_mod+apache with .htaccess turned off is the faster stack. Put a nginx server to server static content in front and that's the fastest stack going forward
Apache has historically been a giant swiss army knife that will do just about everything you could want, from redirect databases to cgi to php interpreters to crazy auth setups. It did all that while still being a reasonably good workhorse for static file serving (when properly turned and using the right worker model, event rather than threaded or process). Nginx seems to have a different model. It does support a num…
nginx is turning into much more than just a load balancer. Projects such as OpenResty (a full CMS built into nginx) and Kong (an API management service), are built right into nginx using Lua. We've done some minor nginx Lua extensions and are looking to offload activities such as JSON validation into the front-end nginx. http://openresty.org/ https://getkong.org
Earlier quoted context omitted.
To summarize your point (and correct me if I'm mistaken), Apache httpd is legacy that people don't seem to want to make the effort to move off of, but still want the benefits of nginx, so they'll stand up nginx in front of httpd, rather than migrate off of Apache (and update their platforms to support that). I feel the "marketing" concept is less actual marketing and more feature appeal, but I guess that's similar? M…
Apache httpd "legacy"? Seems a bit exaggerated. As far as I can tell it works just fine, have plenty of very good tutorials(like those from digital ocean), performance wise no problems(at least for our usage). And seems simpler to setup. At my work we use IIS for our main website, but I've been asked to setup and configure a few wordpress installations. I've played around with both nginx and apache, but it was much e…
The way you're writing, you sound like you've tried one (Apache), and not really the other (nginx) and are basing your opinion on that, not on any merit-based evaluation...
Earlier quoted context omitted.
>Can also be re-written as "Apache Still the dominant web platform for the internet despite the upstarts.." No, it can't. That just misses the entire point of the article. The key take away from it is how much Nginx has grown in the last few years by taking share away from Apache especially those deployments that needed support of modern protocols (from the article: 76.8% of all sites supporting HTTP/2 use Nginx, whi…
I assume boznz meant an entire (different) article could be written with that headline. One can certainly call this or the theoretical opposite article spin.
Earlier quoted context omitted.
HTML itself allows SGML-style tag omission since HTML was originally an application of SGML. A simple example can be found at [1], and can also be seen in action in my talk slides linked from [2]. [1] http://sgmljs.net/docs/html5.html#tag-omission-on-document-l... [2] http://sgmljs.net/blog/blog1701.html
We're talking XML rather than HTML (and omitting certain closing tags isn't compliant HTML5 anyway). In XML there's also the concept of using self-closing tags only for "empty tags". Meaning, isn't "correct" and 123 should be used instead; while s-expressions simplify this.
Nginx is the web server equivalent of programming languages with fibers (in a good way.) Is there anything that competes/a "next Nginx"?
https://caddyserver.com/ Caddy is written in Go, and make use of native fibers/green threads/goroutines.