Not that this will help or hurt your cause for Node.JS, but you can use XMLSERVICE with .Net instead of the IBM i Access drivers.
Last year I wrote a lite wrapper around the XMLCGI interface that can be used by any .Net developer to access IBM i services via XMLSERVICE.
Feel free to expose your .Net team to this and they can do performance comparisons.
http://xmlservicei.codeplex.com/
They can also use XMLCGI by themselves without my wrapper but it's more work.
Either way your entire dev team can use XMLSERVICE including PHP, Ruby, Node and .Net developers.
Regards,
Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
Visit me on: Twitter | LinkedIn
------------------------------
message: 3
date: Sat, 10 Oct 2015 04:37:39 +0000
from: Kelly Cookson <KCookson@xxxxxxxxxxxx>
subject: Re: [WEB400] Why does node's Toolkit for i, use a database
connection to execute CL commands?
Nathan,
I am too new to all of this to have a lot of expectations. I grew up on the IBM i as an OPM COBOL developer, and I still pretty much do OPM COBOL development when it comes to the IBM i. So I'm mostly trying to figure out how things work with node on the IBM i.
The only .NET interface that I have heard about is the .NET Provider. This reflects my knowledge, not what might be available.
It seems to me that node offers more flexibility than the .NET Provider in terms of access to IBM i resources. They can both use SQL to perform CRUD operations on DB2 files. They can both call CL, RPG and COBOL programs, though you have to create stored procedures to do so with the .NET Provider. Toolkit for i (using XMLSERVICE) lets node access some resources that the .NET Provider cannot, like data queues, user spaces, individual CL commands, user profiles, and more.
I am curious whether or not node scales more efficiently than the .NET Provider in terms of concurrent users. I develop apps used by employees. We have about 4,000-5,000 employees and growing. We're definitely not talking large-scale by Internet standards. I suspect both node and the .NET Provider can handle 4,000-5,000 concurrent users. I'm just curious which handles concurrent users more efficiently in terms of CPU%.
Thanks,
Kelly
midrange.com
