Home/ Questions/Q 7509501
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T22:56:08+00:00

I have been a java web application developer,and now I work on .net framework.

  • 0

I have been a java web application developer,and now I work on .net framework.

When I work in java web,we use the tomcat/jboss to deploy our application. I thought the tomcat/jboss is web server.

When I work in asp.net, I use IIS to deploy the application,then I thought the IIS is another kind of web server.

These days,I am learning rails,then I heard the nginx. From google,it is also a kind of web server.

However I found that some people said we can use nginx and IIS together,or other combination.

Now,I am confused,in my opinion a web server should handle request from the client and return the result.

Each web server should have its own suitation,for example, tomcat for java,iis for asp.net.

But why apache/nginx?

BTW,I do not mean apache/nginx is useless,I am just not Familiar with this.

I wonder if someone can explain it for me?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    First things first: a “web server” is just a piece of software that serves content over the http(s) protocol. That’s the minimum functionality. So you threw around a lot of additional features…

    JBOSS/Tomcat is not only a “web server”; a tomcat provides functionality to have a java application responding to requests sent to that server, a JBOSS is much more, it provides special techniques “to deploy” your software into the production environment, and more…

    All these products have the “web server” functionality, but they distinguish in what happens behind the http request, that’s what’s generating the “answer”.

    To confuse you a little more, you can run ASP.NET in an apache web server (that has to be extended with facilities to “execute .NET code”). And of course you can build composites of all these products, since the http protocol can be used by proxies. For example you can use an apache web server as client access point that authenticates against some database and then forwards the requests to a firewalled IIS server that only allows connections from the apache. So you can implement an authentification (or load balancer) that may be unsupported on your windows server…

    Hope that cleared some things…

    rob

    • 0