Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

DevOps for Django - The Best Deployment Strategy

DZone's Guide to

DevOps for Django - The Best Deployment Strategy

· DevOps Zone ·
Free Resource

Planning to extract out a few microservices from your monolith? Read this free guide to learn the best practice before you get started.

Deploying Django is hard according to blogger Randall Degges.  His initial post about Django deployment got a lot of attention from some big time developers in the Django community.  What he decided to do as a result was to start documenting the best deployment strategies around for Django and post them.  Right now he's just outlined what he wants to do, which he will follow up with his company's specific use case for Django and pain points:

In an perfect world, as a developer, I should be able to:

  • Run a single command to deploy my application into production.
  • Run a single command to automatically scale up (or scale down) my application.
  • Instantly add services to my infrastructure that my application needs (memcachedredis,postgresql, etc.).
  • Have full access to logs and metrics for all parts of my infrastructure, so that I can find problems and fix them based on facts, not assumptions.
Furthermore,  I want my application and all of its related infrastructure components to *just work*, and require NO maintenance.  -- Randall Degges


Degges admits that a lot of the problem isn't centered on Django but the fact that he's working with so many technologies, services, and libraries to make a Django stack do what he wants.  Such is life in open source land.

Source: http://rdegges.com/devops-django-part-1-goals


Learn how to measure the impact of every feature release on performance and customer experience metrics.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}