Django vs Phoenix Framework

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Django
Django

8K
5.8K
+ 1
2.9K
Phoenix Framework
Phoenix Framework

461
467
+ 1
613
Add tool

Django vs Phoenix Framework: What are the differences?

Django: The Web framework for perfectionists with deadlines. Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design; Phoenix Framework: Most web frameworks make you choose between speed and a productive environment. Phoenix gives you both. Phoenix is a framework for building HTML5 apps, API backends and distributed systems. Written in Elixir, you get beautiful syntax, productive tooling and a fast runtime.

Django and Phoenix Framework can be categorized as "Frameworks (Full Stack)" tools.

"Rapid development", "Open source" and "Great community" are the key factors why developers consider Django; whereas "High performance", "Super fast" and "Rapid development" are the primary reasons why Phoenix Framework is favored.

Django and Phoenix Framework are both open source tools. Django with 42.3K GitHub stars and 18.2K forks on GitHub appears to be more popular than Phoenix Framework with 13.9K GitHub stars and 1.75K GitHub forks.

Instagram, Pinterest, and Udemy are some of the popular companies that use Django, whereas Phoenix Framework is used by DNSBL.io, inkl, and The RealReal. Django has a broader approval, being mentioned in 979 company stacks & 882 developers stacks; compared to Phoenix Framework, which is listed in 73 company stacks and 46 developer stacks.

What is Django?

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

What is Phoenix Framework?

Phoenix is a framework for building HTML5 apps, API backends and distributed systems. Written in Elixir, you get beautiful syntax, productive tooling and a fast runtime.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Django?
Why do developers choose Phoenix Framework?

Sign up to add, upvote and see more prosMake informed product decisions

Sign up to add, upvote and see more consMake informed product decisions

What companies use Django?
What companies use Phoenix Framework?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Django?
What tools integrate with Phoenix Framework?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Django and Phoenix Framework?
Flask
Flask is intended for getting started very quickly and was developed with best intentions in mind.
Node.js
Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
Rails
Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.
Laravel
It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.
PHP
Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world.
See all alternatives
Decisions about Django and Phoenix Framework
Node.js
Node.js
Python
Python
MySQL
MySQL
Memcached
Memcached
nginx
nginx
RabbitMQ
RabbitMQ
Redis
Redis
Django
Django
Tornado
Tornado
Varnish
Varnish
HAProxy
HAProxy

Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.

See more
Node.js
Node.js
Python
Python
React
React
Django
Django

In late 2015, following the Series G, Pinterest began migrating their web experience to React, primarily because they “found React rendered faster than our previous template engine, had fewer obstacles to iterating on features and had a large developer community.”

The legacy setup consistent of Django, Python and Jinja on the backend, with Nunjucks handling template rendering on the client side. They wanted to move to React for handling template rendering across the board, but if they “switched the client-side rendering engine from Nunjucks to React, [they’d] also have to switch [their] server-side rendering, so they could share the same template syntax.”

They decided on an iterative approach that consolidated a single template rendering engine between client and server, since “If the server could interpret JavaScript, and use Nunjucks to render templates and share our client-side code, we could then move forward with an iterative migration to React.” The team decided to stand up a Node process, behind Nginx, and interpret JavaScript server-side.

Now, when a user agent makes a request, a latent module render requests that it needs data via an API call. Concurrently, a separate network call is made “to a co-located Node process to render the template as far as it can go with the data that it has.”

Node then responds with rendered templates, and along with a “holes” array to indicate what data was still needed to complete the render. Finally, the Python webapp makes an API call to fetch the remaining data, and each module is sent back to Node as completely independent module requests/in parallel/.

With this framework in place, Pinterest developers are in the process of replacing Nunjucks code with React components throughout the codebase.

See more
Zarema Khalilova
Zarema Khalilova
Frontend Team Lead at Uploadcare · | 8 upvotes · 51K views
atUploadcareUploadcare
Django
Django
Node.js
Node.js
React
React
Gatsby
Gatsby
Netlify
Netlify
#Frontend
#StaticSiteGenerators
#StaticWebHosting

Since 2011 our frontend was in Django monolith. However, in 2016 we decide to separate #Frontend from Django for independent development and created the custom isomorphic app based on Node.js and React. Now we realized that not need all abilities of the server, and it is sufficient to generate a static site. Gatsby is suitable for our purposes. We can generate HTML from markdown and React views very simply. So, we are updating our frontend to Gatsby now, and maybe we will use Netlify for deployment soon. This will speed up the delivery of new features to production.

#StaticSiteGenerators #StaticWebHosting

See more
Tim Abbott
Tim Abbott
Founder at Zulip · | 8 upvotes · 43.5K views
atZulipZulip
Django
Django
Django REST framework
Django REST framework

Zulip has been powered by Django since the very early days of its development with Django 1.4, back in 2012. As a reasonably mature web application with significant scale, we're at the stage in many companies' development where one starts to rip out more and more of the web framework to optimize things or just make them work the way we want. (E.g. while I was at Dropbox in early 2016, we discovered we only had about 600 lines of code left from the original Pylons framework that actually ran).

One of the things that has been really fantastic about Django is that we're still happily using it for the vast majority of code in the project, and every time Django comes out with a new release, I read the changelog and get excited about several improvements that actually make my life better. While Django has made some design decisions that I don't agree with (e.g. I'm not a fan of Django REST framework, and think it makes life more difficult), Django also makes it easy to do your own thing, which we've done to great effect (see the linked article for details on our has_request_variables framework).

Overall I think we've gotten a ton of value out of Python and Django and would recommend it to anyone starting a new full-featured web application project today.

See more
Node.js
Node.js
JavaScript
JavaScript
Django
Django
Python
Python

Django or NodeJS? Hi, I’m thinking about which software I should use for my web-app.