Node.js vs. Play vs. Fat-Free
Related Comparisons
|
|
|
|||||
Node.js |
Play |
Fat-Free |
|||||
Favorites937
|
Favorites42
|
Favorites5
|
|||||
Hacker News, Reddit, Stack Overflow Stats |
|||||||
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 Play?Play Framework makes it easy to build web applications with Java & Scala. Play is based on a lightweight, stateless, web-friendly architecture. Built on Akka, Play provides predictable and minimal resource consumption (CPU, memory, threads) for highly-scalable applications.
|
What is Fat-Free?Fat-Free Framework makes it easy to build entire Web sites in a jiffy. With the same power and brevity as modern Javascript toolkits and libraries, F3 helps you write better-looking and more reliable PHP programs.
|
||||
Pros about this tool |
|
|
|
||||
Cons about this tool |
|
|
|
||||
Companies |
3281 Companies Using Node.js
|
105 Companies Using Play
|
1 Companies Using Fat-Free
|
||||
Integrations |
Node.js
Integrations
|
Play
Integrations
|
Fat-Free
Integrations
|
||||
Latest News |
Node v6.13.0 (LTS)
February 13, 2018
Node.js Error Handling – ERR_CONSOLE_WRITABLE_STREAM
February 12, 2018
Building a realtime polls app with Node.js and Pusher
February 06, 2018
|
Reviews of Node.js, Play, and Fat-Free
Node.js benchmark
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://medium.com/@mihaigeorge.c/web-rest-api-benchmark-on-a-real-life-application-ebb743a5d7a3
Small but powerful
April 02, 2016 11:26
This compact framework provided me flexibility. I can implement my own design pattern either MVC or something else. What caught my attention the most was its built-in ORM that can accommodate SQL and NoSql database. That means I can have my MongoSql and SQL queries written by those compatible raw sql statements but still creates ORM models the same way as nosql. Consider for example: $user=new DB\SQL\Mapper($db,'users');// for sql db $user=new DB\Mongo\Mapper($db,'users'); // for mongo db then $user = $user->load('id = 1');
Thanks to its high modularity, I can add more fat to my liking. There's also Cortex ORM f3 extension which handles join tables. Also, handles sessions, routing, and config with ease and let you organize them neatly. That's just a few of the handful features without much weight and with fast performance. One drawback is smaller community, but didn't disappoint me.
How developers use Node.js vs Play vs Fat-Free
leemunroe uses Node.js
This was my first Node.js app. You could call it experimental. I also used Express.
Klout uses Node.js
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/]
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.
Wikipedia uses Node.js
Wikipedia and other Wikimedia Foundation projects use Node.js for VisualEditor's backend, Parsoid.
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.
Emportant Technologies uses Node.js
Node.js powers our new dashboard which is now super fast even while fetching 10-15 different data views.
WILD uses Node.js
Running all non-static content, from our very own website to social media scrapers.
dei79 uses Node.js
Node.js is the base for the RESTful API and drives all background jobs on the Azure WebSites platform.
israelroldan uses Node.js
Our web gateway is based on node-http-proxy, which allows us to have high performance and scalability.
tarun11ks 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.
wnda uses Node.js
Rather than leverage Grunt.js, which is crap, repetitive tasks like minification can be done through Node.js scripts.
warlyware uses Node.js
I use node as my backend, since I know javascript but I do not know any real backend technologies, with a CLI that can make all kinds of magic happen behind the scenes.
novarac23 uses Node.js
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.
SmartLogic uses Node.js
For JavaScript-heavy Web sites, Node.js makes it possible to reuse the same code on both the client and the server. The evented architecture is particularly well suited for "glue" code that connects other services.
Project Dungeon uses Node.js
Node.js as an asynchronous allows easy scaling of our websocket server for the multiplayer aspect of the game
Merge In uses Node.js
We use Node for our full stack web framework. The native libraries provide unparalleled "isomorphic" functionality.
OdinsHat uses Node.js
Hexo is built on top of NodeJS and I had to use it to create the Deezer Hexo plugin.
hellstad uses Node.js
Natively async for network programming. Reach for Native Addons when you need extra horsepower.
Refractal uses Node.js
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.
lispur uses Node.js
Data pump from Firebase into Apache Nifi. Manages keys to only listen for newest data.
hammyau uses Node.js
The framework the the http server to see the results and manage the documents processed.
Yaakov-Belch uses Node.js
All my web applications and almost all of my command line scripts run on node.js
TriLED uses Node.js
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.
RocketFuel uses Node.js
Node.js is used both for our Frontend tooling and as a basis for some of our API endpoints.
giovannicandido uses Node.js
Platform for the build and command line utilities, for client interface module.
It is not used directly
aleccunningham uses Node.js
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.
aharrisonwatt uses Node.js
Used primary to setup the rest of the stack. NPM is just a amazing tool. Also used for testing simple javascript code straight from the command line.
InsideSales.com uses Node.js
We have some backend microservices written in Node.js throughout the company.
thibmaek uses Node.js
Runs on Node v6+ as a standalone server. Optionally uses nodemon for monitoring of server process.
andfaulkner uses Node.js
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)
HyperTrack uses Node.js
Our web services are end-to-end javascript, powered by Node.js on the server side.
Tinker Travel uses Node.js
Ohh, Non-blocking, JSON embedded, javascriptable event loop server, we love you. Node is quick, easy, extensible, JSON and HTTP native. It's great. We can easily integrate Purescript code with it and even crazier stuff (like Idris https://github.com/statebox/dstbx)
rkdgusrnrlrl uses Node.js
javascript 의 눈부신 발전에 큰 도움이 되준 녀석이다. 빠르게 뭔가 만들고 싶다면, Node.js 가 최고 인것 같다. 그래서 개인 프로젝트는 거의 Node.js로 진행 했다. 작은 단위로 만들어 나가고 빨리 결과물을 볼 수 있어서 나에게 딱 맞는 것 같다.
CB Insights uses Node.js
We use node.js to build backend services as well as middleware for our react-redux frontend applications.
nickdecooman uses Node.js
All backend projects I worked on during the past 3 years use Node at their core (mostly in combination with Express).
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.
Wirkn Inc. uses Node.js
All backend servers at Wirkn are based on Node.js. Our production servers are always kept up to date with the latest LTS version.
mfbx9da4 uses Node.js
Used for web apps, routing, chat clients, backend job systems and web socket apps.
tpkemme uses Node.js
I'm using node modules through npm for this addon. Modules include babel, auto-changelog, and run-when-changed.
Eventvods uses Node.js
Handles the grunt API work, authentication and providing API <-> Cache <-> Database link.
jonathan-fries uses Node.js
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.
TonyManso 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!
mickdekkers uses Node.js
Node.js simplifies development by letting you use a single language on the client and server. This has the added benefit of keeping your apps DRY because you can share code between them.
Its package registry, npm, is the largest of any language. With over 500,000 packages and 500+ new packages being registered every day, you can almost always find what you're looking for. And if you can't, why not make your own and share it with the world?
Scrayos UG (haftungsbeschränkt) uses Node.js
Node.js is used for interactive parts of our homepage, cronjobs and building (gulp). The great performance and asynchronity makes a trustworthy companion in developing live web-parts (socket.io).
akarelas uses Node.js
I use it with webpack & browserify to build my SPA websites or to build linkable libraries for my non-SPA websites
ApertusVR uses Node.js
As part of ApertusVR's JsAPI plugin, Node.js serves REST API, socket API and runs JavaScript plugins.
ujjwalbhujel uses Node.js
Even though, It's full stakers' stuff. It has helped front end way too much with its power full build features and functionality
POROWNEO.PL uses Node.js
As a real-time proxy between frontend and backend components. (socket.io, publish, subscribe, redis, http restful api)
ShadowICT uses Node.js
We use NodeJS as one of the systems for our backends. We use NodeJS primarily when working with apps that need to work in realtime or carry out many actions asynchronously. We also use NodeJS for our custom Nagios and Grafana reporting and monitoring tools.
Virtually(Creative) uses Node.js
Backbone of the Documentation and PostCSS build process for the framework (development).
Not required for use.
elo80ka uses Play
I used Play to build a configuration UI for the service, which let you create and manage the menus (a hierarchical tree of options and actions).
datapile uses Play
Play is a central framework/component/library (not sure what to call things these days) in Scala. We <3 Scala, and therefore we <3 Play.
Play is on of several frameworks we are prototyping and vetting for various public-facing websites, and may ultimately be the framework behind the main datapile.io website.
