Grails
Grails

215
250
86
Node.js
Node.js

26K
7.8K
6.1K
Add tool

Grails vs Node.js: What are the differences?

What is Grails? An Open Source, full stack, web application framework for the JVM. Grails is a framework used to build web applications with the Groovy programming language. The core framework is very extensible and there are numerous plugins available that provide easy integration of add-on features.

What is Node.js? A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. 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.

Grails and Node.js belong to "Frameworks (Full Stack)" category of the tech stack.

"Groovy" is the top reason why over 44 developers like Grails, while over 1320 developers mention "Npm" as the leading cause for choosing Node.js.

Grails and Node.js are both open source tools. It seems that Node.js with 35.5K GitHub stars and 7.78K forks on GitHub has more adoption than Grails with 2.47K GitHub stars and 944 GitHub forks.

reddit, Slack, and MIT are some of the popular companies that use Node.js, whereas Grails is used by PedidosYa, LinkedIn, and Learningpod. Node.js has a broader approval, being mentioned in 4055 company stacks & 3897 developers stacks; compared to Grails, which is listed in 48 company stacks and 22 developer stacks.

What is Grails?

Grails is a framework used to build web applications with the Groovy programming language. The core framework is very extensible and there are numerous plugins available that provide easy integration of add-on features.

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.

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

Why do developers choose Grails?
Why do developers choose Node.js?
What are the cons of using Grails?
What are the cons of using Node.js?
    Be the first to leave a con
    What companies use Grails?
    What companies use Node.js?
    What are some alternatives to Grails and Node.js?
    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.
    Rails
    Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.
    Groovy
    Groovy builds upon the strengths of Java but has additional power features inspired by languages like Python, Ruby and Smalltalk. It makes modern programming features available to Java developers with almost-zero learning curve.
    Android SDK
    Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.
    Django
    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
    See all alternatives
    What tools integrate with Grails?
    What tools integrate with Node.js?
      No integrations found
      Decisions about Grails and Node.js
      No stack decisions found
      Interest over time
      Reviews of Grails and Node.js
      Avatar of mihaicracan
      Web Developer, Freelancer
      Review ofNode.jsNode.js

      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

      How developers use Grails and Node.js
      Avatar of MaxCDN
      MaxCDN uses Node.jsNode.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.

      Avatar of Trello
      Trello uses Node.jsNode.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.

      Avatar of AngeloR
      AngeloR uses Node.jsNode.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.

      Avatar of Tony Manso
      Tony Manso uses Node.jsNode.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!

      Avatar of Tarun Singh
      Tarun Singh uses Node.jsNode.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.

      Avatar of AfricanStockPhoto
      AfricanStockPhoto uses GrailsGrails

      All the power of the JVM, with the ease-of-use of a modern web framework.

      Avatar of Endource
      Endource uses GrailsGrails

      Core component of our bespoke CMS

      How much does Grails cost?
      How much does Node.js cost?
      Pricing unavailable
      Pricing unavailable
      News about Grails
      More news