WSGI Server

WSGI – Web Server Gateway Interface

Formerly Apache configured with mod_python ran most Python web application. However, mod_python wasn’t a standard specification. It was just an implementation that allowed Python code to run on a server.
Therefore the Python community came up with WSGI as a standard interface that modules and containers could implement. WSGI is now the accepted approach for running Python web applications.
Python community came up with WSGI as a standard interface that modules and containers could implement and running Python web applications.

WSGI server simply invokes a callable object on the WSGI application as defined by the PEP 3333 standard

WSGI’s Purpose

WSGI is by design a simple standard interface for running Python code. As a web developer you won’t need to know much more than

• what WSGI stands for (Web Server Gateway Inteface)
• that a WSGI container is a separate running process that runs on a different port than your web server
• your web server is configured to pass requests to the WSGI container which runs your web application, then pass the response (in the form of HTML) back to the requester

If you’re using a standard web framework such as Django, Flask, or Bottle, or almost any other current Python framework, you don’t need to worry about how frameworks implement the application side of the WSGI standard. Likewise, if you’re using a standard WSGI container such as Green Unicorn, uWSGI, mod_wsgi, or gevent, you can get them running without worrying about how they implement the WSGI standard.

However, knowing the WSGI standard and how these frameworks and containers implement WSGI should be on your learning checklist though as you become a more experienced Python web developer.

Original post link