Django vs Laravel vs Node.js

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

Django

23.9K
20.7K
+ 1
3.6K
Laravel

18.5K
14.5K
+ 1
3.4K
Node.js

109.2K
88.8K
+ 1
8.3K

Django vs Laravel vs Node.js: What are the differences?

Django, Laravel, and Nodejs are all web based frameworks to allow web development. Django is a high-level Python Web framework encouraging rapid development that promotes rapid development, clean design and methodical approach. Laravel is a free, open-source PHP web framework, for development of web applications. Laravel follows the model-view architectural pattern based on Symfony. Has a plethora of features such as a modular packaging system with dedicated dependency manager, and different ways for accessing relational databases, and so on. Node.js is an open-source, cross-platform JavaScript run-time environment that executes JavaScript outside of a browser. It is meant for server-side scripting. That is running scripts server-side to produce dynamic web page content.

Advice on Django, Laravel, and Node.js
Needs advice
on
Laravel
Ignite UI
and
CakePHP

Hi, Which tool will you recommend:

I need to build a web application, oriented to small businesses, like a small ERP. It will have intensive use of Sql to access a PostgreSQL database. It has to be secure, as it will handle information on customers, sales, inventory.

If you think another tool will be better, please let that know.

Thanks a lot

See more
Replies (2)
Krunal Shah

Laravel and Postgres will be the better solutions you can add more like Redis for caching and React/Vue for the frontend.

See more
Recommends
Spring Boot

Check Spring, if security and reliability is needed along with Lots of Database , check Spring Data, spring web, spring security

See more
Needs advice
on
Spring Boot
and
Django

I need to build a system(web app) where people will share their projects and will receive funding against those projects if someone likes the projects. The backend should be secure, and the tools that will be needed to build that system should be free. We are a startup that can't invest too much in tools right now. We need to build it in 3-4 four months.

The application should be able to support 10k users for now and should be able to scale later.

Also, please suggest what front-end technologies I should use.

See more
Replies (1)
Top Notch

Depending on the backend I would pick the technology you feel most comfortable with, although, my preference would go to Django with Django REST Framework considering the timeframe you mentioned.

As for the front-end, React.JS and Vue are easy to get started with.

See more
Needs advice
on
Node.js
.NET Core
and
Django

Looking for Advice! I am developing a hybrid app for video streaming, I have a prior experience with .NET Core and would like to use it for my back end but the latest buzz on characteristics of Node.js such as light weight, event loop and Async capabilities is really tempting me to reconsider my decision. On a quick research I could observe that a lot of Internet companies use either Python Django or Node JS for their back end which has thrown me into confusion, looking for an expert advice, thx.

See more
Replies (4)
anas mattar
Technical Lead at DPO International · | 4 upvotes · 33.8K views
Recommends
.NET Core

That's depend on your experience if you are very well in C# you should start using the Technology that's you know and like it.

See more

So none of these tools may be bad for your implementation of this streaming app. But one thing to consider is what are you trying to achieve. If your application is more front end facing with streaming to a backend service C# may be your better implementation path just due to its greater overall versatility in terms of options for mobile, backend development, front end development, service development, etc... However if your focused purely on the streaming aspects and utilizing Amazon or Azure services in conjunction with the language of choice, Python, Node.Js, Django or other technologies may offer a faster option to success. Another thing to consider is many of the streaming platforms today utilize services from cloud vendors to achieve their success more than simply the ingenuity on the part of their internal staff's programming skills. Traditional programming languages like Java, C++, C# are used less these days. Today most teams are piggybacking off these services where its possible to give your application the greatest ability to compete with the big boys. - Your Friendly Neighborhood Tech Manager

See more
Aslam Mohammad
Systems Engineer at Infosys · | 1 upvotes · 23.2K views
Recommends
Node.js
Django

You could apparently go for both Node or Django but I would recommend choosing Node as you're building a video streaming app and the biggest video streaming service Netflix used Node in the production.

See more
Pavel Nekrasov
MyOpenTour at MyOpenTour · | 1 upvotes · 39 views
Recommends
fastapi
at

Take a look at FastAPI if you are going to choose Python

See more
View all (4)
Decisions about Django, Laravel, and Node.js
Christian Stefanescu
Head of IT at lawpilots · | 5 upvotes · 2.7K views

A big part of our needs fits perfectly into what Django has to offer: an ORM with support for PostgreSQL , the amazing auto-generated admin interface, consolidated tooling around the application lifecycle and a well-established community with solutions to the majority of common problems.

We use Django whenever we need the auto-generated admin and the friendly templating language to build capable web applications which are relatively easy to maintain for a comparably long time. The excellent integrations for Celery and Django REST framework make it easy to build the necessary integrations with other services.

See more
Tyrell Perera
Senior Engineering Manager at Telstra · | 4 upvotes · 8.4K views
Migrated
from
Django
to
Spring Boot

I inherited a large Python Django application as part of a corporate re-structure. After careful analysis, working with the new team, we decided to break the monolith into a microservices architecture. While doing so, we managed to port some of those microservices into Spring boot. Better performance and widely available expertise within my current team made me make this decision.

See more

We choose Next.js for our React framework because it's very minimal and has a very organized file structure. Also, it offers key features like zero setups, automatic server rendering and code splitting, typescript support. Our app requires some loading time to process the video, server-side rendering will allow our website to display faster than client-side rending.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Django
Pros of Laravel
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
  • 504
    Clean architecture
  • 364
    Growing community
  • 339
    Composer friendly
  • 315
    Open source
  • 295
    The only framework to consider for php
  • 194
    Mvc
  • 189
    Quickly develop
  • 155
    Dependency injection
  • 143
    Application architecture
  • 129
    Embraces good community packages
  • 57
    Write less, do more
  • 52
    Restful routing
  • 47
    Orm (eloquent)
  • 43
    Artisan scaffolding and migrations
  • 42
    Database migrations & seeds
  • 35
    Awesome
  • 33
    Great documentation
  • 25
    Awsome, Powerfull, Fast and Rapid
  • 25
    Promotes elegant coding
  • 24
    Build Apps faster, easier and better
  • 22
    Easy to learn, scalability
  • 22
    JSON friendly
  • 21
    Most easy for me
  • 21
    Eloquent ORM
  • 19
    Modern PHP
  • 19
    Test-Driven
  • 18
    Beautiful
  • 18
    Blade Template
  • 13
    Security
  • 11
    Based on SOLID
  • 11
    Clean Documentation
  • 10
    Cool
  • 10
    Easy to attach Middleware
  • 10
    Simple
  • 10
    Convention over Configuration
  • 9
    Easy Request Validatin
  • 8
    Simpler
  • 8
    Get going quickly straight out of the box. BYOKDM
  • 8
    Its just wow
  • 8
    Fast
  • 8
    Laravel + Cassandra = Killer Framework
  • 8
    Easy to use
  • 7
    Super easy and powerful
  • 7
    Friendly API
  • 7
    Less dependencies
  • 7
    Simplistic , easy and faster
  • 6
    Great customer support
  • 6
    Its beautiful to code in
  • 5
    Php7
  • 5
    Active Record
  • 5
    Fast and Clarify framework
  • 5
    Easy
  • 5
    The only "cons" is wrong! No static method just Facades
  • 5
    Speed
  • 4
    Eloquent
  • 4
    Easy views handling and great ORM
  • 4
    Minimum system requirements
  • 4
    Laravel Mix
  • 4
    Composer
  • 4
    Laragon
  • 3
    Laravel Nova
  • 3
    Laravel casher
  • 3
    Laravel Spark
  • 3
    Intuitive usage
  • 3
    Ease of use
  • 3
    Cashier with Braintree and Stripe
  • 3
    Laravel Forge and Envoy
  • 3
    Laravel Horizon and Telescope
  • 3
    Laravel Passport
  • 2
    Heart touch
  • 2
    Like heart beat
  • 2
    Touch heart artisan
  • 2
    Scout
  • 2
    Rapid development
  • 2
    Laravel love live long
  • 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 Laravel
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
  • 40
    PHP
  • 27
    Too many dependency
  • 19
    Slower than the other two
  • 15
    A lot of static method calls for convenience
  • 13
    Too many include
  • 10
    Heavy
  • 7
    Bloated
  • 6
    Laravel
  • 5
    Confusing
  • 4
    Does not work well for file uploads in Shared Hosting
  • 3
    Too underrated
  • 2
    Not fast with MongoDB
  • 1
    Difficult to learn
  • 1
    Not using SOLID principles
  • 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 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.

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 Laravel?
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 Laravel?
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
11064
What are some alternatives to Django, Laravel, 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.
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.
Drupal
Drupal is an open source content management platform powering millions of websites and applications. It’s built, used, and supported by an active and diverse community of people around the world.
See all alternatives
Reviews of Django, Laravel, and Node.js
Review of
Laravel

I moved from .NET and Rails to Laravel, and since then never thought to go back. I feel Laravel framework has the capability to overcome all modern frameworks.

At Soft Pyramid we are developing rich business applications using Laravel Framework, and never feel any limitation even for complex reporting.We have written REST apis, complex ERP solutions and found awsome in all areas.

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, Laravel, 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.

bright machine uses
Laravel

The best PHP framework right now, intuitive and growing up quickly.

We use Laravel in the outer layer of our Clean Architecture codebases, whereby the domain model does not rely on the framework as a whole.

Kent Steiner uses
Laravel

See "PHP", I don't really choose to use it, but I can step in and operate in Laravel when necessary. Same goes for quite a few other PHP frameworks, including my own full-featured proprietary stack.

Nicholas Alexander uses
Laravel

An excellent PHP framework employing SOLID principles to rapidly develop web-site systems and connect them to databases. Custom development of admin screens for website management.

Doug Bromley uses
Laravel

A clean, easy to understand, well documented framework with excellent tools and a great community providing every imaginable extension to add functionality to your project.

Kang Hyeon Ku uses
Django

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

Jake Taylor uses
Laravel

Laravel is the PHP framework we use. It speeds up development and simplifies a lot of PHP. Complicated at first but saves time once you're comfortable with it.

Seungkwon Park uses
Django

django는 저의 무기입니다.

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

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