Nitin Nain

Category: Django

Tips on most commonly encountered issues in using Django and Python for Web Development.

  • Why is Kubernetes also called k8s

    Kubernetes is abbreviated as “K8s” to shorten it’s length. There are 8 characters in “Kubernetes” between the first letter “K” and the last letter “s”.

    There are a few other places in the software industry where you might have noticed this style of abbreviation: I saw it first in “i18n” for “internationalization” (from where it seems to have started). There’s also l10n for “localization”.

    – n7n

  • Setting up Django on Windows IIS Server

    This post is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

    (more…)

  • Why, When, and How to use Celery with Python

    “Celery is an asynchronous task queue based on distributed message passing.”

    Let’s break that down:

    (more…)

  • Django’s Request-Response Cycle

    Understanding the Request-Response Cycle is a crucial step in setting up for any WebServer.

    An example of the request-response cycle is when you “request” a web page by entering a URL in your browser and a web server sends a web page as ‘response’ to your browser. Of course, there’re usually several HTTP requests that happen when visiting a website; each is a separate Request-Response in itself.

    The request-response architecture of a web application is an important idea to grasp whether you’re working on Django, Symphony, Laravel, Flask, WordPress or any of the thousands of other web frameworks.

    When you call a Django server the flow typically is

    Request: Browser → Web Server → WSGI → WSGI callable function in Django

    Response: Django → WSGI → Web Server → Browser

    Here’s a diagram that explains the request-response flow very well.

    Django's Request-Response Call Cycle