The Architecture of Open Source Applications: Nginx

Re:The Architecture of Open Source Applications: Nginx by davidw on Monday November 23, 2015 @05:10PM (#10617695)

> Although Apache provided a solid foundation for future development, it was architected to spawn a copy of itself for each new connection

That's not really correct:

https://httpd.apache.org/docs/2.2/mod/prefork.html

Nginx makes it easier to handle a bunch of concurrent connections, but it's not as if Apache simply forks for each new connection.

[ Parent | on HN ]

Re:The Architecture of Open Source Applications: Nginx by lobster_johnson on Monday November 23, 2015 @05:17PM (#10617746)

You're quoting from a paragraph that's summarizing the history of Apache, and the statement was true about Apache 1.x.

Back in the day, Apache 2.0 took a long time to gain substantial market share, for various reasons. The situation was not too dissimilar from the current Python 2/3 split.

Edit: But I guess Apache never forked for every connection, even in 1.3. It only forked if it needed a new child and the existing ones were busy.

[ Parent | on HN ]

Re:The Architecture of Open Source Applications: Nginx by davidw on Monday November 23, 2015 @05:21PM (#10617764)

> the statement was true about Apache 1.x.

Apache 1.3 did not fork a process per connection. It forked to handle additional concurrent connections, but that's very different than forking for each and every connection.

[ Parent | on HN ]