Hacker News, Reddit, Stack Overflow Stats
No public GitHub repository stats available
|Why people like using this tool||
Companies using this service
August 02, 2017 15:18
I have benchmarked Node.js and other popular frameworks using a real life application example. You can find the results here: https://email@example.com/web-rest-api-benchmark-on-a-real-life-application-ebb743a5d7a3
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.
Node is used by ghost, so for my personal blog I mainly work with configuration files, site structure, templates, and a little bit of database related work.
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/]
last time i used the android sdk was converting the tiktok app to ios. what a mess it was back then. the developer nature of the sdk was apparent vs apples offering.
Native android app with features such as event app, lead retrieval app, checkin app, session scanning, badge printing and ticket sales.
The Android SDK is the key-component of all Android-based development and had to be included in this stack for sure. We work with the SDK through IntelliJ IDEA and the command-line.
Uso del Android SDK para el desarrollo de aplicaciones para Android con geolocalización, multimedia y almacenamiento en la base de datos.
So we very, very early on, we were iOS only, then we thought, well we’re missing out on half of the market. We need to add Android. So we had a friend of ours start working on the Android app, and I had to build the API for him, but I was having a really hard time doing that because I didn’t know what he needed exactly, so I built the first version of the web store over the weekend because I wanted to have a client to consume myself for the API I was building.
some backend process. and Unity ( the game engine that roster plus base on) use C# and .Net Library.
Server side development language and frameworks: ASP.Net MVC 4, Asp.Net WebApi 2, Razor View engine, Moq, Entity Frameworks, etc.
As we started on Windows Phone we use C# and .NET for most of our apps and sites. Being a small team of 2, using .NET enables us to work on each part of the service without having to switch to different languages.
Microsoft has done an incredible job of keeping the .NET Framework powerful and stable. It is well designed and keeps getting more robust with each release. It isn't the most popular technology in this space, but I think a good case can be made to use .NET in many new projects.