Get Advice Icon

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

ASP.NET
ASP.NET

13K
302
+ 1
0
Django
Django

7.8K
5.6K
+ 1
2.8K
Add tool

ASP.NET vs Django: What are the differences?

ASP.NET: An open source web framework for building modern web apps and services with .NET. .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications; Django: The Web framework for perfectionists with deadlines. Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

ASP.NET and Django can be primarily classified as "Frameworks (Full Stack)" tools.

Django is an open source tool with 42.6K GitHub stars and 18.3K GitHub forks. Here's a link to Django's open source repository on GitHub.

According to the StackShare community, Django has a broader approval, being mentioned in 993 company stacks & 914 developers stacks; compared to ASP.NET, which is listed in 76 company stacks and 76 developer stacks.

- No public GitHub repository available -

What is ASP.NET?

.NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.

What is Django?

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

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

Why do developers choose ASP.NET?
Why do developers choose Django?
    Be the first to leave a pro

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

      Be the first to leave a con

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

      What companies use ASP.NET?
      What companies use Django?

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

      What tools integrate with ASP.NET?
      What tools integrate with Django?

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

      What are some alternatives to ASP.NET and Django?
      ASP.NET Core
      A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.
      PHP
      Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world.
      JavaScript
      JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
      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.
      Python
      Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best.
      See all alternatives
      Decisions about ASP.NET and Django
      HAProxy
      HAProxy
      Varnish
      Varnish
      Tornado
      Tornado
      Django
      Django
      Redis
      Redis
      RabbitMQ
      RabbitMQ
      nginx
      nginx
      Memcached
      Memcached
      MySQL
      MySQL
      Python
      Python
      Node.js
      Node.js

      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
      Django
      Django
      React
      React
      Python
      Python
      Node.js
      Node.js

      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 · 47K views
      atUploadcareUploadcare
      Netlify
      Netlify
      Gatsby
      Gatsby
      React
      React
      Node.js
      Node.js
      Django
      Django
      #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 · | 7 upvotes · 29.8K views
      atZulipZulip
      Django REST framework
      Django REST framework
      Django
      Django

      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
      Python
      Python
      Django
      Django
      JavaScript
      JavaScript
      Node.js
      Node.js

      Django or NodeJS? Hi, I’m thinking about which software I should use for my web-app. What about Node.js or Django for the back-end? I want to create an online preparation course for the final school exams in my country. At the beginning for maths. The course should contain tutorials and a lot of exercises of different types. E.g. multiple choice, user text/number input and drawing tasks. The exercises should change (different levels) with the learning progress. Wrong questions should asked again with different numbers. I also want a score system and statistics. So far, I have got only limited web development skills. (some HTML, CSS, Bootstrap and Wordpress). I don’t know JavaScript or Python.

      Possible pros for Python / Django: - easy syntax, easier to learn for me as a beginner - fast development, earlier release - libraries for mathematical and scientific computation

      Possible pros for JavaScript / Node.js: - great performance, better choice for real time applications: user should get the answer for a question quickly

      Which software would you use in my case? Are my arguments for Python/NodeJS right? Which kind of database would you use?

      Thank you for your answer!

      Node.js JavaScript Django Python

      See more
      Benjamin Bernard-Bouissières
      Benjamin Bernard-Bouissières
      Web Developer at ipexia · | 11 upvotes · 44.4K views
      atipexiaipexia
      PythonAnywhere
      PythonAnywhere
      Symfony
      Symfony
      Python
      Python
      Django
      Django

      I really love Django because it is really fast to create a web application from scratch and it has a lot a facilities like the ORM or the Admin module ! The Python language is really easy to read and powerful, that's why I prefer Django over Symfony.

      I use Django at work to make tools for the technicians but I also use it for me to build my personal website which I host on PythonAnywhere.

      See more
      Greg Neumann
      Greg Neumann
      Indie, Solo, Developer · | 6 upvotes · 75.8K views
      TypeScript
      TypeScript
      Vue.js
      Vue.js
      Electron
      Electron
      Quasar Framework
      Quasar Framework
      ASP.NET
      ASP.NET
      Xamarin Forms
      Xamarin Forms
      .NET Core
      .NET Core
      Xamarin
      Xamarin

      Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

      This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

      But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

      I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

      Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

      See more
      Michael Mota
      Michael Mota
      CEO & Founder at AlterEstate · | 4 upvotes · 980 views
      Next.js
      Next.js
      Graphene
      Graphene
      GraphQL
      GraphQL
      Django
      Django

      I've been using Django for quite a long time and in my opinion I would never switch from it. My company is currently using Django with REST framework and a part in GraphQL using Graphene. On the frontend we use Next.js and so far everything has been running quite good. I've found limitations but manage to solve it.

      As someone mentioned before, if you are comfortable with Django, don't switch. There's no need since with django you can basically achieve anything. Of course this will depend on the project you want to build, but the scalability and flexibility django can offer it's just out of this world. (Don't want to sound like a fan boy haha but it really is).

      See more
      Interest over time
      Reviews of ASP.NET and Django
      No reviews found
      How developers use ASP.NET and Django
      Avatar of MOKA Analytics
      MOKA Analytics uses DjangoDjango

      Django takes the hassle out of building an enterprise web application using Python.

      • admin app for administration
      • ORM for deploying against different database vendors
      • social auth package for authentication with enterprise IdP
      • guardian package for authorization
      Avatar of Yaakov Gesher
      Yaakov Gesher uses DjangoDjango

      Our backend was written in Django. We took advantage of the ready-to-go admin interface as a go-to solution for the client to be able to authorize his users, as well as other functionality, while most of the work was done through the Django Rest Framework.

      Avatar of Blair Gemmer
      Blair Gemmer uses DjangoDjango

      Hands down the best Python web framework I've used. Very easy to extend and add apps and go from 0 to full project quickly and painlessly. I built a fully authenticated project with a single endpoint in less than 30 minutes.

      Avatar of Kang Hyeon Ku
      Kang Hyeon Ku uses DjangoDjango

      정말 편리하고 많은것을 알아서 제공해 주는 프레임워크 이다. 책의 예제만 진행해서 많이 써보지는 못했지만, 쉽게 쉽게 웹을 개발 할 수 있는 점이 매력적 이다. 게다가 orm 이 기본으로 내장 되어 있고 db 도 sqlite 가 기본으로 되어있어. 그냥 django 만 설치하면 바로 웹개발이 가능하다.

      Avatar of Seungkwon Park
      Seungkwon Park uses DjangoDjango

      django는 저의 무기입니다.

      django 이외에 flask로 간단한 restful api를 만들면서 느낀점은 framework 보다 언어가 중요하다는것을 알았고 django가 얼마나 큰 framework인지 알게되었습니다.

      저는 signal 사용을 좋아합니다.

      How much does ASP.NET cost?
      How much does Django cost?
      Pricing unavailable
      Pricing unavailable
      News about ASP.NET
      More news