|Hacker News, Reddit, Stack Overflow Stats|
|Why people like using this service||
|Companies using this service|
Feeling like when I learned ruby on rails
March 07, 2016 09:55
The Framework is new but has what it takes to take your apps to the next level, right now rails 5 is beta with ActionCable to make real time but I must say ruby isn't the right tool for doing real time but Elixir is really fast and has great concurrency and other erlang features.
I'm using node modules through npm for this addon. Modules include babel, auto-changelog, and run-when-changed.
All backend servers at Wirkn are based on Node.js. Our production servers are always kept up to date with the latest LTS version.
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.
All backend projects I worked on during the past 3 years use Node at their core (mostly in combination with Express).
We use node.js to build backend services as well as middleware for our react-redux frontend applications.
NodeJS drove the app's backend server (ExpressJS), frontend build tools (Gulp and Webpack), linters (ESLint), and most of the database scripts (through Knex and Mongoose)
→ Lab9 Bot
Runs on Node v6+ as a standalone server. Optionally uses nodemon for monitoring of server process.
In order to speed up loading times and allow SEO, a separate node server runs along side the Django server to render React components serverside and return the rendered HTML.
Platform for the build and command line utilities, for client interface module.
It is not used directly
A lot of our tools that run on our IoT devices are written in Node.js. The simplicity & async nature of Node.js makes it very easy and efficient to develop and maintain these tools.
All my web applications and almost all of my command line scripts run on node.js
The framework the the http server to see the results and manage the documents processed.
Most of the code we write on the server-side is in Node, due to it's flexibility, ease of use and extremely quick runtime once setup correctly.
Natively async for network programming. Reach for Native Addons when you need extra horsepower.
We use Node for our full stack web framework. The native libraries provide unparalleled "isomorphic" functionality.
I use node.js mainly for backend-utility and data management scripts.
Node.js as an asynchronous allows easy scaling of our websocket server for the multiplayer aspect of the game
When ever there is a need for real time, event driven , non-blocking things this is my go to. It filles in the spots where Rails could not and it does that very well.
Rather than leverage Grunt.js, which is crap, repetitive tasks like minification can be done through Node.js scripts.
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.
Our web gateway is based on node-http-proxy, which allows us to have high performance and scalability.
Node.js is the base for the RESTful API and drives all background jobs on the Azure WebSites platform.
Node.js powers our new dashboard which is now super fast even while fetching 10-15 different data views.
We decided to move the provisioning process to an API-driven process, and had to decide among a few implementation languages:
We built prototypes in both languages, and decided on NodeJS:
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.
Wikipedia and other Wikimedia Foundation projects use Node.js for VisualEditor's backend, Parsoid.
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.
The social ranking platform, Klout, used to use a PHP & LAMP stack but found it difficult to continue to scale, so when they had the chance they moved to a Node.js backend. They even wrote about switching to Node.js and how they use it. [additional source: http://blog.klout.com/2011/10/the-tech-behind-klout-com/]
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.
정말 편리하고 많은것을 알아서 제공해 주는 프레임워크 이다. 책의 예제만 진행해서 많이 써보지는 못했지만, 쉽게 쉽게 웹을 개발 할 수 있는 점이 매력적 이다. 게다가 orm 이 기본으로 내장 되어 있고 db 도 sqlite 가 기본으로 되어있어. 그냥 django 만 설치하면 바로 웹개발이 가능하다.
→ My Stack
django는 저의 무기입니다.
django 이외에 flask로 간단한 restful api를 만들면서 느낀점은 framework 보다 언어가 중요하다는것을 알았고 django가 얼마나 큰 framework인지 알게되었습니다.
저는 signal 사용을 좋아합니다.
Quick development of standalone sites for smaller projects, REST APIs and basic CMS work.
We use django CMS for our primary website. It's flexible, easy to use, and it seems to perform very well.
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.
Django framework provides the web application framework, session modules, database and templates.
Django (and Python in general), lets us write concise, readable, and reasonably high-level code.
Used for templating, the ORM (database management), file management (user-uploaded content), and for the REST framework package.