Web server:handles HTTP Request
App Server:handle The business logic of the application
1) Web server
A Web server mainly deals with sending HTML for display in a Web browser. When a request comes into the Web server, the Web server simply passes the "request to the" program best able to handle it. The Web server doesn ' t provide any functionality beyond simply providing a environment in which the Server-side program C An execute and pass back the generated responses.
2) App Server
An application server provides access to business logic for use by client application programs. The application program can use this logic just as it would call a method on an object
3) Example
Weblogic, Websphere------> App Server
Apache-----> Web Server
Tomcat, IIS-----> a light-weight Application Server
Tomcat: Early Tomcat was a Jsp/servlet interpretation engine embedded in Apache Apache+tomcat equivalent to iis+asp. Later Tomcat is no longer embedded in Apache, and the Tomcat process runs independently of the Apache process. Furthermore, Tomcat is already a standalone servlet and JSP container, and the business Logic layer code and interface interaction layer code can be separated. So, someone called Tomcat a lightweight application server.
IIS: Microsoft's early IIS is a purely Web server. Later, it embeds an ASP engine that interprets VBScript and JScript server-side code, which can be used concurrently as an application server. Of course, it doesn't compare with the Java EE Application Server at all, but, functionally speaking, it can be called the application server in principle. To be exact, it is a Web server with a bit of application server functionality.
The different between app server and Web server