Djangoย vsย .NET Coreย vsย Node.js

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

Django

23.9K
20.7K
+ 1
3.6K
.NET Core

2K
1.6K
+ 1
108
Node.js

108.1K
88.8K
+ 1
8.3K
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Django
Pros of .NET Core
Pros of Node.js
  • 619
    Rapid development
  • 459
    Open source
  • 394
    Great community
  • 344
    Easy to learn
  • 256
    Mvc
  • 208
    Beautiful code
  • 207
    Elegant
  • 187
    Free
  • 186
    Great packages
  • 173
    Great libraries
  • 63
    Restful
  • 60
    Powerful
  • 59
    Comes with auth and crud admin panel
  • 55
    Great documentation
  • 52
    Great for web
  • 41
    Python
  • 35
    Great orm
  • 31
    Great for api
  • 24
    All included
  • 20
    Web Apps
  • 19
    Fast
  • 16
    Used by top startups
  • 14
    Clean
  • 13
    Sexy
  • 12
    Easy setup
  • 10
    Convention over configuration
  • 7
    ORM
  • 7
    Allows for very rapid development with great libraries
  • 7
    The Django community
  • 5
    Its elegant and practical
  • 5
    Great MVC and templating engine
  • 4
    Full stack
  • 4
    Mvt
  • 4
    Easy Structure , useful inbuilt library
  • 4
    Fast prototyping
  • 4
    Easy to develop end to end AI Models
  • 3
    Easy
  • 3
    Easy to use
  • 3
    King of backend world
  • 3
    Cross-Platform
  • 3
    Batteries included
  • 3
    Have not found anything that it can't do
  • 2
    Scaffold
  • 2
    Zero code burden to change databases
  • 2
    Full-Text Search
  • 2
    Map
  • 2
    Modular
  • 2
    Very quick to get something up and running
  • 2
    Many libraries
  • 2
    Python community
  • 2
    Great peformance
  • 2
    Just the right level of abstraction
  • 1
    Easy to change database manager
  • 23
    Perfect to do any backend ( and a fast frontend) stuff
  • 18
    Cross-platform
  • 17
    Great performance
  • 16
    Fast
  • 13
    It promotes better codebase architectures and organizat
  • 13
    All Platform (Mac, Linux, Windows)
  • 8
    Very fast development with templates
  • 1.4K
    Npm
  • 1.3K
    Javascript
  • 1.1K
    Great libraries
  • 1K
    High-performance
  • 791
    Open source
  • 480
    Great for apis
  • 471
    Asynchronous
  • 417
    Great community
  • 387
    Great for realtime apps
  • 292
    Great for command line utilities
  • 78
    Node Modules
  • 76
    Websockets
  • 65
    Uber Simple
  • 53
    Great modularity
  • 53
    Allows us to reuse code in the frontend
  • 38
    Easy to start
  • 33
    Great for Data Streaming
  • 29
    Realtime
  • 25
    Awesome
  • 23
    Non blocking IO
  • 16
    Can be used as a proxy
  • 15
    High performance, open source, scalable
  • 14
    Non-blocking and modular
  • 13
    Easy and Fun
  • 12
    Same lang as AngularJS
  • 11
    Easy and powerful
  • 10
    Future of BackEnd
  • 9
    Fast
  • 8
    Scalability
  • 8
    Cross platform
  • 8
    Fullstack
  • 7
    Mean Stack
  • 7
    Simple
  • 5
    Easy concurrency
  • 5
    Great for webapps
  • 5
    React
  • 4
    Friendly
  • 4
    Easy to use and fast and goes well with JSONdb's
  • 4
    Typescript
  • 4
    Fast, simple code and async
  • 3
    Its amazingly fast and scalable
  • 3
    Scalable
  • 3
    Great speed
  • 3
    Fast development
  • 3
    Isomorphic coolness
  • 3
    Control everything
  • 2
    It's fast
  • 2
    Not Python
  • 2
    Blazing fast
  • 2
    One language, end-to-end
  • 2
    TypeScript Support
  • 2
    Easy to learn
  • 2
    Javascript2
  • 2
    Easy to use
  • 2
    Less boilerplate code
  • 2
    Sooper easy for the Backend connectivity
  • 2
    Great community
  • 2
    Scales, fast, simple, great community, npm, express
  • 2
    Performant and fast prototyping
  • 1
    Easy
  • 1
    Lovely
  • 0
    Event Driven

Sign up to add or upvote prosMake informed product decisions

Cons of Django
Cons of .NET Core
Cons of Node.js
  • 24
    Underpowered templating
  • 19
    Underpowered ORM
  • 18
    Autoreload restarts whole server
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 7
    Not nodejs
  • 7
    Admin
  • 6
    Configuration hell
  • 3
    Not as clean and nice documentation like Laravel
  • 3
    Bloated admin panel included
  • 3
    Python
  • 2
    Overwhelming folder structure
  • 2
    Not typed
  • 1
    InEffective Multithreading
    Be the first to leave a con
    • 46
      Bound to a single CPU
    • 40
      New framework every day
    • 34
      Lots of terrible examples on the internet
    • 28
      Asynchronous programming is the worst
    • 22
      Callback
    • 16
      Javascript
    • 11
      Dependency based on GitHub
    • 10
      Dependency hell
    • 10
      Low computational power
    • 7
      Can block whole server easily
    • 6
      Very very Slow
    • 6
      Callback functions may not fire on expected sequence
    • 3
      Unneeded over complication
    • 3
      Unstable
    • 3
      Breaking updates
    • 1
      No standard approach

    Sign up to add or upvote consMake informed product decisions

    What is Django?

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

    What is .NET Core?

    Cross-platform (supporting Windows, macOS, and Linux) and can be used to build device, cloud, and IoT applications.

    What is 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.

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

    What companies use Django?
    What companies use .NET Core?
    What companies use Node.js?

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

    What tools integrate with Django?
    What tools integrate with .NET Core?
    What tools integrate with Node.js?

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

    Blog Posts

    Oct 24 2019 at 7:43PM

    AppSignal

    +8
    5
    685
    Oct 3 2019 at 7:13PM

    Ably Realtime

    +8
    4
    3197
    +6
    1
    1116
    +5
    7
    1620
    +29
    15
    11071
    What are some alternatives to Django, .NET Core, and Node.js?
    Flask
    Flask is intended for getting started very quickly and was developed with best intentions in mind.
    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.
    WordPress
    The core software is built by hundreds of community volunteers, and when youโ€™re ready for more there are thousands of plugins and themes available to transform your site into almost anything you can imagine. Over 60 million people have chosen WordPress to power the place on the web they call โ€œhomeโ€ โ€” weโ€™d love you to join the family.
    See all alternatives
    Reviews of Django, .NET Core, and Node.js
    Web Developer, Freelancer
    Review of
    Node.js

    I have benchmarked Node.js and other popular frameworks using a real life application example. You can find the results here: https://medium.com/@mihaigeorge.c/web-rest-api-benchmark-on-a-real-life-application-ebb743a5d7a3

    How developers use Django, .NET Core, and Node.js
    MaxCDN uses
    Node.js

    We decided to move the provisioning process to an API-driven process, and had to decide among a few implementation languages:

    • Go, the server-side language from Google
    • NodeJS, an asynchronous framework in Javascript

    We built prototypes in both languages, and decided on NodeJS:

    • NodeJS is asynchronous-by-default, which suited the problem domain. Provisioning is more like โ€œstart the job, let me know when youโ€™re doneโ€ than a traditional C-style program thatโ€™s CPU-bound and needs low-level efficiency.
    • NodeJS acts as an HTTP-based service, so exposing the API was trivial

    Getting into the headspace and internalizing the assumptions of a tool helps pick the right one. NodeJS assumes services will be non-blocking/event-driven and HTTP-accessible, which snapped into our scenario perfectly. The new NodeJS architecture resulted in a staggering 95% reduction in processing time: requests went from 7.5 seconds to under a second.

    Trello uses
    Node.js

    The server side of Trello is built in Node.js. We knew we wanted instant propagation of updates, which meant that we needed to be able to hold a lot of open connections, so an event-driven, non-blocking server seemed like a good choice. Node also turned out to be an amazing prototyping tool for a single-page app. The prototype version of the Trello server was really just a library of functions that operated on arrays of Models in the memory of a single Node.js process, and the client simply invoked those functions through a very thin wrapper over a WebSocket. This was a very fast way for us to get started trying things out with Trello and making sure that the design was headed in the right direction. We used the prototype version to manage the development of Trello and other internal projects at Fog Creek.

    AngeloR uses
    Node.js

    All backend code is done in node.js

    We have a SOA for our systems. It isn't quite Microservices jsut yet, but it does provide domain encapsulation for our systems allowing the leaderboards to fail without affecting the login or education content.

    We've written a few internal modules including a very simple api framework.

    I ended up picking Node.js because the game client is entirely in JavaScript as well. This choice made it a lot easier for developers to cross borders between being "client side" game developers and "server side" game developers. It also meant that the pool of knowledge/best practices is applicable almost across the company.

    Tony Manso uses
    Node.js

    Node.js is the foundation for the server. Using Express.js for serving up web content, and sockets.io for synchronizing communications between all clients and the server, the entire game runs as Javascript in Node.js.

    I don't know how well this will scale if/when I have hundreds of people connected simultaneously, but I suspect that when that time comes, it may be just a matter of increasing the hardware.

    As for why I chose Node.js... I just love JavaScript! My code is all original, meaning that I didn't have to inherit anyone's bad Javascript. I'm perfectly capable of creating my own bad Javascript, thank you! Also, npm rocks!

    Tarun Singh uses
    Node.js

    Used node.js server as backend. Interacts with MongoDB using MongoSkin package which is a wrapper for the MongoDB node.js driver. It uses express for routing and cors package for enabling cors and eyes package for enhancing readability of logs. Also I use nodemon which takes away the effort to restart the server after making changes.

    MOKA Analytics uses
    Django

    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
    Yaakov Gesher uses
    Django

    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.

    Blair Gemmer uses
    Django

    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.

    Kang Hyeon Ku uses
    Django

    ์ •๋ง ํŽธ๋ฆฌํ•˜๊ณ  ๋งŽ์€๊ฒƒ์„ ์•Œ์•„์„œ ์ œ๊ณตํ•ด ์ฃผ๋Š” ํ”„๋ ˆ์ž„์›Œํฌ ์ด๋‹ค. ์ฑ…์˜ ์˜ˆ์ œ๋งŒ ์ง„ํ–‰ํ•ด์„œ ๋งŽ์ด ์จ๋ณด์ง€๋Š” ๋ชปํ–ˆ์ง€๋งŒ, ์‰ฝ๊ฒŒ ์‰ฝ๊ฒŒ ์›น์„ ๊ฐœ๋ฐœ ํ•  ์ˆ˜ ์žˆ๋Š” ์ ์ด ๋งค๋ ฅ์  ์ด๋‹ค. ๊ฒŒ๋‹ค๊ฐ€ orm ์ด ๊ธฐ๋ณธ์œผ๋กœ ๋‚ด์žฅ ๋˜์–ด ์žˆ๊ณ  db ๋„ sqlite ๊ฐ€ ๊ธฐ๋ณธ์œผ๋กœ ๋˜์–ด์žˆ์–ด. ๊ทธ๋ƒฅ django ๋งŒ ์„ค์น˜ํ•˜๋ฉด ๋ฐ”๋กœ ์›น๊ฐœ๋ฐœ์ด ๊ฐ€๋Šฅํ•˜๋‹ค.

    Seungkwon Park uses
    Django

    django๋Š” ์ €์˜ ๋ฌด๊ธฐ์ž…๋‹ˆ๋‹ค.

    django ์ด์™ธ์— flask๋กœ ๊ฐ„๋‹จํ•œ restful api๋ฅผ ๋งŒ๋“ค๋ฉด์„œ ๋Š๋‚€์ ์€ framework ๋ณด๋‹ค ์–ธ์–ด๊ฐ€ ์ค‘์š”ํ•˜๋‹ค๋Š”๊ฒƒ์„ ์•Œ์•˜๊ณ  django๊ฐ€ ์–ผ๋งˆ๋‚˜ ํฐ framework์ธ์ง€ ์•Œ๊ฒŒ๋˜์—ˆ์Šต๋‹ˆ๋‹ค.

    ์ €๋Š” signal ์‚ฌ์šฉ์„ ์ข‹์•„ํ•ฉ๋‹ˆ๋‹ค.