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

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

Alternatively you could use proper JavaScript via Node.js and the cache.node / iris.node interface :-)

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-feature

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

No, I won't be there, sorry

Rob

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-ewdxpr...

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

In the meantime, enjoy!

Rob

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

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

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

Alternatively...

For those interested in exploring and using MicroServices with all versions of Cache today, QEWD.js has provided a very cool set of Open Source solutions and advanced functionality for a year now.

The full detail is described in the following parts of the Online QEWD.js Course:

https://www.slideshare.net/robtweed/ewd-3-training-course-part-43-using-json-web-tokens-with-qewd-rest-services

https://www.slideshare.net/robtweed/ewd-3-training-course-part-44-creating-microservices-with-qewdjs

https://www.slideshare.net/robtweed/ewd-3-training-course-part-45-using-qewds-advanced-microservice-functionality

And QEWD.js is an ideal and very powerful, modern Open Source REST platform for Cache.  See:

https://www.slideshare.net/robtweed/ewd-3-training-course-part-31-ewdxpress-for-web-and-rest-services

 And all for free :-)

This is one of those things that becomes dead easy when you use Node.js (and use QEWD to integrate Cache with Node).  There's almost always a tried and tested module out there already that will do the stuff you want, eg in this case:

https://www.npmjs.com/package/csvtojson

And once in JSON format, you can transform it to whatever other JSON format you want using:

https://github.com/robtweed/qewd-transform-json

QEWD supports Cache Objects for those who wish to use them via the cache.node APIs for Cache Objects.:

https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY...

Your handler logic (which runs in a QEWD Worker process) has access to these APIs via the "this.db" object, eg this.db.invoke_classmethod()

The following post is a bit old and refers to how you used these APIs in EWD.js.  However, change the invocation to this.db.xxx() and the examples should work in QEWD:

https://groups.google.com/forum/#!searchin/enterprise-web-developer-comm...

Personally I prefer to use the Cache database as a persistent JSON database / Document Database, via the ewd-document-store abstraction that is used by QEWD, and integrate that storage into JavaScript Objects.  But Cache Objects will work with QEWD and GraphQL just fine

Rob

As I release my code as Open Source, I've no idea of usage stats.  There's growing interest in the use of GraphQL in the community I work within these days, for all sorts of reasons.

QEWD is a re-badging of EWD 3, so yes, it is supported in QEWD - which of course is straightforward since QEWD is JavaScript/Node.js and can just use the Facebook JavaScript GraphQL module.

Just making the point that GraphQL and support for it in Cache isn't something new, as those who follow our work at M/Gateway will know :-)

Rob

Just for the record, GraphQL access to Cache has been supported in EWD.js and EWD 3 (the fore-runners to QEWD.js) since 2015:

https://groups.google.com/forum/#!searchin/enterprise-web-developer-comm...

https://groups.google.com/forum/#!searchin/enterprise-web-developer-comm...

You could take a look at this, which was originally designed, some 4 years ago, to provide browser-based terminal roll&scroll access to VistA.   If you're familiar with Node.js, you should be able to adapt it for your own use:

https://github.com/robtweed/ewdVistATerm