Node.js vs. Django vs. Laravel



Hacker News, Reddit, Stack Overflow Stats

  • 3.86K
  • 4.31K
  • 258K
  • 2.49K
  • 5.14K
  • 188K
  • 516
  • 3.17K
  • 106K

GitHub Stats

Description

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.

What is Django?

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

What is Laravel?

Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Laravel 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.

Want advice about which of these to choose?Ask the StackShare community!

Pros

Why do developers choose Node.js?
Why do you like Node.js?

Why do developers choose Django?
Why do you like Django?

Why do developers choose Laravel?
Why do you like Laravel?

Cons

What are the cons of using Node.js?
Downsides of Node.js?

What are the cons of using Django?
Downsides of Django?

What are the cons of using Laravel?
Downsides of Laravel?

Companies

What companies use Node.js?
4693 companies on StackShare use Node.js
What companies use Django?
1144 companies on StackShare use Django
What companies use Laravel?
975 companies on StackShare use Laravel

Integrations

What tools integrate with Node.js?
95 tools on StackShare integrate with Node.js
What tools integrate with Django?
25 tools on StackShare integrate with Django
What tools integrate with Laravel?
16 tools on StackShare integrate with Laravel

What are some alternatives to Node.js, Django, and Laravel?

  • Rails - Web development that doesn't hurt
  • Android SDK - The Android SDK provides you the API libraries and developer tools necessary to build, test, and debug apps for Android.
  • .NET - .NET is a free, cross-platform, open source developer platform for building many different types of applications.
  • Spring-Boot - Create Spring-powered, production-grade applications and services with absolute minimum fuss

See all alternatives to Node.js

Latest News

Node v6.13.0 (LTS)
Node.js Error Handling – ERR_CONSOLE_WRITABLE_STREAM
Building a realtime polls app with Node.js and Pusher
Django security releases issued: 2.0.2 and 1.11.10
2017 Malcolm Tredinnick Memorial Prize awarded to Cl...
The DSF Welcomes Carlton Gibson as its Newest Fellow
Laravel Zero 5.6 is Now Released
LaraStream – A Laravel live stream community
Building a Vue SPA with Laravel Part 3
Related Stack Decisions
Zarema Khalilova
Zarema Khalilova
Frontend Team Lead at Uploadcare · | 7 upvotes · 2776 views
atUploadcare
Netlify
Gatsby
React
Node.js
Django
#StaticWebHosting
#StaticSiteGenerators
#Frontend

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
Antonio Sanchez
Antonio Sanchez
CEO at Kokoen GmbH · | 8 upvotes · 3865 views
atKokoen GmbH
ExpressJS
Node.js
JavaScript
MongoDB
Go
MySQL
Laravel
PHP

Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

See more
Russel Werner
Russel Werner
Lead Engineer at StackShare · | 8 upvotes · 6136 views
atStackShare
Redis
CircleCI
Webpack
Amazon CloudFront
Amazon S3
GitHub
Heroku
Rails
Node.js
Apollo
Glamorous
React
#FrontEndRepoSplit
#Microservices
#SSR
#StackDecisionsLaunch

StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

#StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

See more


Interest Over Time