Re: ibm_db node module and IBM Data Server Driver

Also, they don't really need .Net Core to start building .Net web services to IBMi. The standard .Net components still work fine with the ADO.Net Database Drivers and ODBC.

At the moment there is no super-compelling reason to switch to .Net Core unless you want to do multi-platform hosting, which is my interest in it.

Regards,

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

-----Original Message-----
message: 5
date: Tue, 10 Apr 2018 12:55:29 +0000
from: Tim Fathers <X700-IX2J@xxxxxxxxxxx>
subject: Re: [WEB400] ibm_db node module and IBM Data Server Driver

But we've started to gradually replace green screen development with .NET web front-ends.

...so where does Angular/React fit in here? I'm a tad confused (as usual!) about the mix of .NET and the JS frameworks for the front-end. Especially in the light of this sentence...

If we adopt node, then we could also take advantage of .NET Core JavaScript Services, which allows .NET apps to incorporate node modules and custom JavaScript functions running on node on windows.

...which seems to imply .NET on the server side?

In any case, I think my advice would remain the same - make your existing backend application available as a web service. If you have .NET developers writing fat clients then I would refactor these so that they no longer communicate with the IBM i via ADO but using web service calls too, this gives you many advantages, not least of which means that you can use exactly the same web services to write web applications as you can to write your .NET clients.