My FeedDiscussionsHeadless CMS
New
Sign in
Log inSign up
Learn more about Hashnode Headless CMSHashnode Headless CMS
Collaborate seamlessly with Hashnode Headless CMS for Enterprise.
Upgrade ✨Learn more

Time to migrate to NodeJS?

Daniel Lobo's photo
Daniel Lobo
·Nov 27, 2017

Some time ago we had contact with Grails 1, and found it great to create web apps quickly. So time has passed, started a new application using Grails 2. Two years later and after recently migrating from grails 2 to 3, we're feeling the app can't handle itself anymore with its more than 600k lines of code, a memory footprint of ~1.7GB and a horrendous startup time (1~2m on server, even worse at my dev desktop).

Some of our secondary applications are written in JavaScript, like reports, telemetry and internal monitoring. And we are surprised with NodeJS memory footprint (around 100~120MB) and startup speed.

So, given the age of NodeJS (not a recent tech), the IDEs who support the language (Netbeans, IntelliJ...), number of libraries it has and general trends, can it be a viable solution to migrate the main application to NodeJS?

p.s.: Our starting plan is migrating in parts, using microservices, for example. the frontend would be the last one to be decommissioned.

p.s.2: We tried to minimize those simptoms, like remove some dependencies and optimize code, but we reached a point where it's too much effort for little gain.

Feel free to ask if something important is missing here