Re: Rise of Node

I don't believe your .Net teams need to get of the .Net database drivers to start moving to .Net core. They can develop with .Net core and .Net drivers as long as they deploy on Windows.

Or start using .Net core for most new stuff, but create a standard .Net data service so the .Net drivers are used in one web service layer.

I have also built an opensource .Net core wrapper around the XMLSERVICE component that works with .Net core on Windows, Linux or Mac.

You could also write CGI or Node on IBMi to create JSON web services for them to consume from .Net or .Net core.

Even the IBMi IWS server can do that.

And if they want to use the JT400 data services to IBMi, I wrapped JT400 to work with .Net using an open source component called IKVM.

I guess the takeaway on that is that whether they want to use Node or not with IBMi, there are multiple data options the team can use.

Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------

message: 2
date: Sun, 18 Mar 2018 15:45:56 +0000
from: Kelly Cookson <KCookson@xxxxxxxxxxxx>
subject: Re: [WEB400] [EXTERNAL] Re: Rise of Node

On the comparison of adopting Node and Java...

My shop refused to adopt Java on the IBM i because: (1) we were
already using .NET, and (2) database drivers and stored procedures
were sufficient for the few times we needed to make .NET interact with DB2 and COBOL.

Node is different for our shop for a variety of reasons.

* Using Node would let our .NET developers stop using ADO.NET to
interact with the IBM i. Getting rid of dependency on ADO.NET would
let them move to .NET Core.