ExpressJS vs. Django REST framework vs. Sails.js

Extremely lean framework for our Node API.

Used it in Node.js for routing

Main application framework

Webserver

website back-end functionality, front-end/backend messaging bridge (websocket <-> gearman communication)

We rely on ExpressJS to serve our content simply, easily, and effectively, without the bloat-ware. Big thanks to StrongLoop for supporting this package.

All our APIs use Express

Powers the web interface for events API as well as the admin dashboard.

Allows for server side data access and simple templating.

API framework

Isomorphic rendering of Jade templates and React components. Some components may be lazy-loaded.

Our microservices are mostly written using Node.js, and ExpressJS is the framework upon which all of our Node.js services are built.

Express.js is the workhorse of the Cloudcraft.co backend. It's not the most exciting part of a stack, but it works, is very well documented, and you can find a plugin for almost everything you could possibly want. We also carefully evaluated Koa.js, but decided not to go down this route: fewer plugins, less documentation & answers online. I'm also not personally convinced by the generators yield syntax at all. ES7 async functions looks like a much better bet, and with Promises and Babel I can have that already today.

Handles the front-end events.

We used Express to serve up our Angular front-end.

Serve our statistics data.

https://ifunny.co

Front-end API

My preferred framework for web applications running on node, used primarily to render React components on a node server.

Used Express.js for web application development.

Wrote dispatcher as a router and middleware service.

Backend is powered built on express nodejs framework

ExpressJS powers the API on an associated nodejs server.

We use Express as our main router and do clever things with it to produce our AMP pages.

use template from webstorm. intuitive. evaluating.

Powers the HTTP API platform.

Express is critical to the Node.js app, particularly express-session for session tracking.

Express, of course, fits very well with Ng2 as its server solution.

Glup server type uasge

Used to quickly build server for client application.

node.js 접하자 마자 접함 웹프레임 워크 경량화되 많은 기능을 직접 구현되지 않고 만들거 쓰거나 가져다 써야 하지만, 그런 점이 node 와 잘 맞는 것 같다.

Front-end web server.

Used Express as the foundation of every Node.JS based API I worked on.

Backend of dashboard at Chaordic dashboard, freelancing products with upwork and personal projects

I'm fluent in ExpressJS, but over the past two years I have moved to HapiJS. Similar results, but I find Hapi to be more full-featured towards my app, api and service needs. I can operate confidently in both.

expressgen set everything up. Views in pug.

API driven microservices

Least opinionated and easiest to hack around with.

We use Express.js on top of Node.js to create our controllers.

To run the server that will be used to connect and collaborate the Hololens in the classroom.

Robust and reliable back-end & API routing.

For our REST API.

Django REST delivered all the content to the BI, making calls to the Postgres DB, aggregating numeric data, and automatically associating data models at the time of row creation.

Provides REST API

Instead of using Django for both back and frontend, I use DRF to layout an API that ReactJs can pull data from. Easy to setup, well documented, and works seamlessly with React.

django에서 api를 만드는데 최고의 framework라고 생각합니다. 아직은 tutorial 수준의 class base view, function base view 수준으로 사용합니다.

하지만 현재 진행중인 프로젝트의 심화로 REST framework를 심도있게 다룰 예정입니다.

Project is mainly a RESTful service project, so DRF had a a huge role in it.

For our backend REST API

Really great framework for building RESTful APIs. Lots of plugins for it!

Easy to use

Sails serves the API backend