If you haven’t had the opportunity to read our series focused on “What is Legacy Code”, it might help to quickly catch-up and review that first. When modernizing IBM i AS400 in IT environments, there are considerations to make.
Most of our customers are comfortable with RPG since it is the predominant language on the AS400 (now IBM i), and most are familiar with Java and .NET since those languages have been around for 2-3 decades. Many developers are not as familiar with Node.js. There are a lot of great resources available regarding Node.js. I though amalgamating that information into one concise article for ease of reference might be a better use of your time. There are many resources surrounding Node.js. Here is a list of the top things you should consider before choosing a language for your development.
Everyone has an Opinion, but this is your Decision
There are a few things that are key to remember on your digital transformation journey. Just as it’s not up to me or any vendor to define what is legacy and what is modern, it’s also not up to me or any vendor to define what is your preferred target language. It is up to each organization, and by organization I mean the affected units within the organization, to collaborate and have detailed conversations on this topic as it relates to their specific business needs. Gone are the days when IT can have one view, and business another. The companies that survive and thrive have an aligned and unified definition of not only where they are, but also where they want to be.
As you think of your target language options, be sure to follow these steps:
- Ask experts for guidance
- Perform assessment/due diligence
- Check target language resource availability and rates
- Do a proof of concept
- Rest confidently in and move forward with your informed decision
Look to Data, Not Emotions, to Drive your Target Language Decision
Modernizing IBM i AS400 with Node.js
In addition, here are some great facts that support the use of Node.js over other languages:
- Node.js helps reduce developing costs by 58%, according to Netguru. Remember, transforming RPG to Node.js is only part of the solution…you must think about ongoing development in that target language once you arrive to your target language destination.
- 49.9% of professional developers use Node JS for its frameworks, libraries, and tools, according to Stack Overflow. And Profound.js is a framework that brings enterprise data processing standards to Node.js in a way that Node.js programmers are used to using.
- More than 85 countries and users with 45 different native languages use Node.js worldwide, according to NodeJS. So, as we are no longer companies that are focused on one geography as our playground, this type of statistic is extremely relevant as you consider scaling worldwide.
- 46% of Node.js developers are in the group age 25-35, according to NodeJS. That is to say that a similar concern of RPG developers retiring is not going to raise its head again for 50+ years.
- All versions of Node.js show a 40% year-by-year growth of downloads, according to Nodesource and Nodesource Insights. Compare this trend with those of .NET and Java.
Continue to watch for future articles in this series, all done with the hope to make your digital transformation of legacy applications successful. And if any of my colleagues at Profound Logic or I can help along the way, please don’t hesitate to contact us!