In that case I'll wait for a different competition :-)

That depends on your definition of "REST API on the Intersystems IRIS side".  That Intersystems IRIS provides the HTTP interface?  and/or the code that does the work of the API is within IRIS and therefore ObjectScript?  As far as QEWD is concerned, Intersystems IRIS is simply a persistent JSON store with no other role (though you still can invoke ObjectScript methods and access classes if you want), so a REST API is implemented in JavaScript and handled by Node.js/QEWD.  

So, provided Intersystems IRIS is used as the back-end database for the data persistence of the APIs, the competition allows the use of any other technologies in front of it?  eg QEWD/Node.js + browser UI?

These competitions appear to demand the use of Cache ObjectScript rather than any other language.  Is this correct?  And if so, why can't other languages be used instead?

Try using this interface module instead: https://github.com/chrisemunt/mg-dbx

They aren't products as such, more repositories that focus on particular aspects of / components within QEWD, to help people get up and running with them.  They are linked from the main QEWD repository, which, in turn, is linked to your Open Exchange. 

QEWD is already listed, Evgeny. 

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?

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

Evgeny

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

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?

Submitted now, awaiting approval

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?

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

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

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

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

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.

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