Hurricane is an initiative to fit Django perfectly with Kubernetes.
Project description
Hurricane
An initiative to fit Django perfectly with Kubernetes. It is supposed to cover many capabilities in order to run
Django in a cloud-native environment, including a Tornado-powered Django app server.
Explore the docs »
Hurricane website
·
User's guide
·
Guide to the first Hurricane-based Application
Intro
Django was developed with the batteries included-approach and already handles most of the challenges around
web development with grace. It was initially developed at a time when web applications got deployed and run on a server
(physical or virtual). With its pragmatic design it enabled many developers to keep up with changing requirements,
performance and maintenance work.
However, service architectures have become quite popular for complex applications in the past few years. They provide
a modular style based on the philosophy of dividing overwhelming software projects into smaller and more controllable
parts. The advantage of highly specialized applications gained prominence among developers, but introduces new
challenges to the IT-operation.
However, with the advent of Kubernetes and the cloud-native development philosophy a couple of new possibilities emerged
to run those service-based applications even better. Kubernetes is a wonderful answer for just as many IT-operation
requirements as Django is for web development. The inherent monolithic design of Django can be tempting to roll out
recurring operation patterns with each application. It's not about getting Django to run in a
Kubernetes cluster (you may already solved this), it's about integrating Django as tightly as possible with Kubernetes
in order to harness the full power of that platform. Creating the most robust, scalable and secure applications
with Django by leveraging the existing expertise of our favorite framework is the main goal of this initiative.
Hurricane is supposed to make the most out of the existing Django ecosystem without reinventing the wheel. We will collect best-practices and opinions about how to run Django in Kubernetes and put them on Hurricane's roadmap.
Application Server
Why another app server instead of uwsgi, gunicorn or mod_wsgi? We need a cloud-native app server which is
much more tidily coupled to the Django application itself. Think of special url routes for Kubernetes probes! Building a
special View in each and every Django application is not an appropriate solution. What about the Kubernetes Metrics API?
That's all something we don't want to take care of in our Django code.
Those traditional app servers (i.e. uwsgi et.al.) have a highly optimized process model for bare-server deployments with
many CPUs, multiple threads and so on. In Kubernetes the scaling of an application is done through the Replication-value
in a workload description manifest. This is no longer something we configure with app server parameters.
Installation
Hurricane can be installed from a Python Package Index:
pip3 install hurricane
Add "hurricane" to your INSTALLED_APPS:
INSTALLED_APPS += (
'hurricane',
)
Check out the documentation for more information and a user's guide.
Commercial Support
Hurricane is developed and maintained by Blueshoe. If you need any help implementing with hurricane, please contact us: hurricane@blueshoe.de.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for django_hurricane-1.0.0-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | 9d777db015b9535dd3335605b35588da8d3f2a03b16a3cfda534a2209a9bc4f1 |
|
MD5 | cb209bb2879ed6e5255463db803f4aa4 |
|
BLAKE2b-256 | a2a49760d8f4899761e28b15ed9324424c498c49a00a37268f62d79c6dea843f |