As QEWD makes use of the InterSystems Node.js connector which is available for both Cache and IRIS, the answer is yes. 

If you can provide me access to an IRIS system on GCP Cloud, then sure.

What functionality would you like to see, and what would the target audience be?

Note: I'm not around to do anything until early September

Rob

Can you provide me with an IRIS license and cover the cost of the GCP Cloud Hosting for the purpose of a demo?

Thanks Ward for raising awareness of the QEWD / IRIS demo while I'm away!

Evgeny - I'm on holiday right now and quickly integrated IRIS with the Conduit / RealWorld back-end code before I left - I didn't have much time and hadn't tested the demo out.  It's actually an interesting "hybrid" version of the back end that works with both WebSockets (the version you see in this demo) and REST (which you would see if you pointed a "vanilla" Conduit front-end at it.  

I pushed out a new version of QEWD to formally integrate IRIS, and also a new supporting module: 

https://github.com/robtweed/ewd-qoper8-iris

Just specify the database type as "iris" in your QEWD startup file, and provide the other parameters (username, password, namespace etc) just as for Cache.

Needless to say, the demo you see works identically, with exactly the same Node.js code, for all supported databases, so you'll just have to take my word, for now, that it really is working with IRIS! :-)  Actually the performance will indicate that it's hooked up to a pretty fast DB (and yes, it really is IRIS, running on an AWS EC2 Ubuntu machine): see the response time recorded in the raw response messages that you'll see if you enable your browser's JavaScript console.  All the data is being stored in IRIS as persistent JSON - see Slide decks (part 17 onwards) here:

http://docs.qewdjs.com/qewd_training.html

When I get back from holiday, time-permitting, I intend to put together some proper, updated source code for the Conduit app that people can try for themselves, using pure REST (which is probably what many / most want to see) and also (again time-permitting) do a MicroService-based version. 

However, the code base you've found will give you an initial idea how a QEWD / IRIS application would be written (though there have been some enhancements that have simplified some of the coding still further since I wrote the Conduit app).  This slide deck is up to date and explains the way you write REST apps these days:

https://www.slideshare.net/robtweed/ewd-3-training-course-part-31-ewdxp…

I'll also check out the Comments asap to see if / why they aren't working as you report.

In the meantime, enjoy!

Rob

No, I won't be there, sorry

Rob

OK I fixed the comments bug

Also I've started a separate posting about QEWD and IRIS - https://community.intersystems.com/post/using-qewdjs-create-rest-apis-iris

Yes, InterSystems dropped the idea of implementing JavaScript as an integrated language.  Never mind, for those who haven't seen this, here's how (and why) it's been achieved anyway:

https://www.slideshare.net/robtweed/data-persistence-as-a-language-feat…

That's a code sequencing issue.  Change the end of Ward's qewd-start.js file to this:

let qewd = require('qewd').master;
// define the internal QEWD Express module instance

// start the QEWD server now ...
qewd.start(config);

let xp = qewd.intercept();
// define a basic test path to test if our QEWD server is up- and running
xp.app.get('/testme', function(req, res) {
  console.log('*** /testme query: ', req.query);
  res.send({
    hello: 'world',
    query: req.query
  });
});

and it should work for you

BTW you can further simplify and optimise the performance of Ward's forEachChild() logic like this:

customerNode.forEachChild(function (customerId, childNode) {
  if (childNode.$(['Address', '1']).value === 'London') {
    // do what's needed with a London customer ...
  }
});

ie by using the childNode argument of the forEach() and using the $ array feature

Rob

Fabian

You misunderstand: ewd-document-store is an abstraction built on top of the InterSystems Node.js client, NOT an alternative to it.  QEWD uses the InterSystems Node.js client via ewd-document-store, so once again, QEWD isn't an alternative to the Node.js client, but makes it a lot easier to use with IRIS or Cache.

You can't directly filter objects with IRIS NoSQL storage (aka Global Storage) - instead the trick it to maintain indices to optimise iteration - see Ward's follow-up comment., and study those slide decks I've created that describe how to use QEWD's abstraction of Global Storage.

OK some further digging reveals that the main problem is that QEWD is freezing at the point where it tries to start the Node.js Express web server. 

I'd guess the reason is either:

- something to do with the way Express works internally that clashes with iris-main; or

- port 8080 (which is the port I'm telling Express to listen on) being unavailable because of something IRIS has done

Anyone have any clues?

There's a second problem which is that the Node.js setInterval() function appears to freeze iris-main - something that is pretty critical to have working in QEWD

I don't have accounts on GCP or Azure and am not familiar with their use.  I use AWS EC2 all the time so I know how to work with it.  The problem is unlikely to be AWS-specific, however

One further observation: setInterval() definitely hangs everything.  However setTimeout() works just fine

Ok forget all that - I've figured out how to make it work and will report back later with the solution :-)

OK I seem to be on my own sorting this out...but I seem to have figured it all out.  I had to first adapt the changePassword utility to work on my derived Container, and once that was done I could use the System Management Portal - which showed me that the Callin Interface wasn't enabled.  Once I enabled that, QEWD burst into life :-)

So a question (if anyone out there is listening) - is there a configuration setting somewhere to enable the callin interface automatically when you start up the container, ie to avoid the need to manually enable it via the System Management Portal?

Submitted now, awaiting approval

I provided an external article link.  What do you suggest I use instead.

I entered the version number of QEWD as 2.44.23 which is what it is set to on NPM - why has this been queried?

Evgeny

I seem to be stuck in "awaiting approval" status, so am unable to make the change you're wanting

Why aren't they made available using NPM, which is where a Node.js developer would expect to find such modules?

One limitation I can see straight away is that this version only includes outdated files for Node.js (ie the iris*.node files).  All I see is iris610.node and iris700.node.  Is there a reason why the Node.js version 8 and version 10 interface files haven't been included?