Member Avatar for DB216

I have been asked to "Analyse & Compare the Key Features of IIS 6.0 & Apache 2.0" I have to present it to my management team and it should not be to "Techie". I have found plenty on IIS but am struggling on Apache 2.0. Any details on Security, Reliability, Scalability and Ease of Use would be ideal as that is the headings I have for IIS. Many thanks. DB

  • 2 Contributors
  • 5 Replies
  • 298 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by Zachery

Dani AI

Generated

A short, management-level summary of Apache 2.0 that builds on 's point about matching the server to the application stack and gives the four comparison headings you requested.

Apache 2.0 introduced a redesigned core (the Apache Portable Runtime, a new module API, and a pluggable Multi-Processing Module model) that makes the server more portable and easier to tune for different operating systems and workloads. This architecture is the reason Apache can be optimized per-site (for example, by choosing a different MPM) rather than using a one-size-fits-all engine. (httpd.apache.org)

Security and reliability: TLS support is provided as an integrated module (mod_ssl) and the 2.0 architecture makes it straightforward to enable or disable features via modules. The project documents practical hardening steps (keep the server and modules patched, run the server with least privilege, restrict writable paths, minimize enabled modules, and monitor logs). Applied properly, Apache 2.0 is stable and can be hardened to enterprise standards. (httpd.apache.org)

Scalability and performance: the MPM model (prefork, worker, perchild) controls how Apache handles concurrency. Prefork gives process isolation (good if you rely on non-thread-safe modules), worker uses threads for better throughput and lower memory, and platform-specific MPMs (for example the Windows winnt module) let the server use native APIs for better performance on that OS. The filter framework and modules such as mod_deflate and the rewritten mod_proxy enable efficient compression, proxying, and reverse-proxy/load‑balancing patterns. (httpd.apache.org)

Ease of use and management: configuration was simplified in 2.0 (fewer confusing directives, clearer virtual-host handling), and dynamic module (DSO) support changed how modules are loaded so admin workflows differ from 1.3-era Apache. Expect text-based configuration as the default; many GUI front-ends and distribution packages add management wrappers on top of that. When preparing a comparison for management, emphasize: (1) application compatibility (match the app stack), (2) operational model (text-config + module management), and (3) maintenance commitment (patching and module discipline). (httpd.apache.org)

Summary: Apache 2.0 is a mature, modular server designed for flexibility and portability. For a non-technical management slide, present one line per heading (Security: configurable and hardenable; Reliability: production-proven; Scalability: tunable via MPMs; Ease of Use: file-based configs, many third-party GUIs).

Recommended Answers

All 5 Replies

Member Avatar for Zachery

DB,

What sort of applications are you going to be running, do you have a choice between linux and windows or, windows running IIS and windows running Apache.

How much expirence do you have with IIS over apache?

Are you confortable with config files or do you need a UI ?

Member Avatar for DB216

Zachery,
Whatever solution, IIS or Apache, will most probably sit on a windows server system. I won't personally be running it, I just have to present the main features of each to management so they can make an informed decision on what to go for. As I said I have loads of info on IIS but not much on Apache. I know it is the most popular choice with around 70% of web hosts using it but what are its key features that I can compare to IIS. Stability, Security, Ease of management, Scalability etc DB

Member Avatar for Zachery

Well like I said, if you are going to be running ASP.net apps theres no logical reason to run apache ;)

Abit more insight would help one way or another. Apache has been around a long time, and is a long standing httpd server in the linux world, less used in the windows world, since its time tested and tempered it has less security issues. It will run about par with IIS in terms of real world preformance at least in realition to php / mysql sites.

Member Avatar for DB216

Makes sense. Are you saying IIS has improved enough to equal Apache and is Apache totally at home sitting on a windows server? DB

Member Avatar for Zachery

It really depends on your application.

If you are going to be running asp and asp.net apps there is NO REASON to run apache, because theres no support for it

If you are going to be running a php site, you have a 50/50 shot, with it, depending on your setup and your specific NT OS

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.