Big News: FounderDating is joining OneVest to build the largest community for entrepreneurs. Details here
Latest Notifications
You have no recent recommendations.
Name
Title
 
MiniBio
FOLLOW
Title
 Followers
FOLLOW TOPIC

Question goes here

1,300 Followers

  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur

Apache or nginx?

These two are the most common open source web servers. Each of them has its pros and cons. I would like to know which one is your choice and why?

6 Replies

Andrea Raimondi
0
0
Andrea Raimondi Entrepreneur
Computer Software Consultant and Contractor
What are you trying to do?
Tim Boudreau
0
0
Tim Boudreau Entrepreneur
Consulting Product Manager / Software Engineer at Oracle Labs
NginX, without question. Unless you need some Apache-specific feature, Apache's process-oriented design is very dated and inefficient, and, because of its design and the need for backward compatibility, unable to take full advantage of asynchronous I/O features in modern operating systems. Apache was designed for a different era, when web applications ran inside the web server itself and were likely to be Perl scripts.

The one case I can think of for using Apache in this day and age is if you're using PHP - and if you are, then the efficiency of your web server is the least of your problems.
Rob Mitchell
0
0
Rob Mitchell Entrepreneur
Senior Java Software Engineer at Direct Commerce
I've used Apache most of my life, but recently started looking at nginx and I am very impressed. And I certainly love the idea of embedding the server into my Java app which seems much more trivial these days and tends to gain a lot of flexibility for very little effort. Just my opinion.
Sebastien Mirolo
0
0
Sebastien Mirolo Entrepreneur
Subscription Product Engineering
nginx always. Maybe Apache if you are trying to deploy a PHP site.
Garet Claborn
1
0
Garet Claborn Entrepreneur
CEO, Original Author at Approach Corporation
NGINX.

Not to say there aren't viable configurations for Apache, like MPM, and other candidates for server software. When it comes to PHP, nginx with PHP FPM (which is now built in) is very fast.

Personally I believe that tales of balanced "pros and cons" are almost entirely synthetic. Apache, in the hands of a very experienced admin, can do well at threading but even at it's best is a resource hog.

PRO-Apache:

1. Deeper configuration scripting options for less common networks, caching scenarios and services.

2. More tutorials online. Familiar, respected.

PRO-NGINX:

1. Very clean architecture, fewer things can go wrong once you've got it right.

2. Massively threaded.

3. Lightweight memory footprint and processor usage

4. Far above apache in serving static content

5. Can use the more common apache configurations and has some unique abilities.

6. Modern concerns taken into account during design of NGINX


ANTI-Apache:

1. Bloated. SO SO bloated. Do not underestimate the level of resource drain that is caused in the majority case. Experienced admins may fine tune it but there's only so much you can really do. You need more CPU and more RAM to run the same site at the same traffic level.

2. Complex. While more people are used to Apache due to its age and near monopoly early on, the average admin of those I've met are not masters of it. There are many nuances to any web server, but especially Apache imho.

3. Apache's detailed config scripts are both a pro and a con. You don't want to have to debug a configuration. While things like "EasyApache" exist, most scripted installs are not optimized for your situation.

4. Declining support, industry slowly moving on.Even Apache 2 is based on partially outdated code.

5. Totally subjective, but Apache was once my favored server. I can hardly stand to use it anymore, I feel that NGINX has spoiled me.


ANTI-NGINX:

1. Slightly less community support / tutorials online. Not in short supply by any means, though.

2. If you are accustomed to Apache already, you'll have to learn a little bit.

3. Some of the NGINX nuances are annoying, like sockets sometimes need. a little help depending on which distro you use. Nothing major.

4. NGINX Pro. AFAIK Apache is 100% open source. NGINX is trying to monetize the product directly, which means some good features may be withheld from the base offering. It seems this mostly relates to cloud clustering however which neither do out of the box anyway.


Stephen Packer
1
0
Stephen Packer Entrepreneur
Lead Developer at Lettuce Box LLC
Caddy.It's performant like Nginx, HTTPS by default and auto-generates SSL certificates for free using LetsEncrypt, and easy to configure.
Join FounderDating to participate in the discussion
Nothing gets posted to LinkedIn and your information will not be shared.

Just a few more details please.

DO: Start a discussion, share a resource, or ask a question related to entrepreneurship.
DON'T: Post about prohibited topics such as recruiting, cofounder wanted, check out my product
or feedback on the FD site (you can send this to us directly info@founderdating.com).
See the Community Code of Conduct for more details.

Title

Give your question or discussion topic a great title, make it catchy and succinct.

Details

Make sure what you're about to say is specific and relevant - you'll get better responses.

Topics

Tag your discussion so you get more relevant responses.

Question goes here

1,300 Followers

  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
Know someone who should answer this question? Enter their email below
Stay current and follow these discussion topics?