No disrespect to what you've created, but I have to say I'm always amazed and dismayed at how complex the Java community always seem to manage to make even the simplest of tasks - Spring/Hibernate is a classic example of making a crazy mountain out of what should technically be a very simple mole-hill.
If you're interested in trying out the mgweb-server Docker Container (aka mg_web Server Appliance) with an IRIS back-end (eg using the IRIS Community Edition Docker Container), I've put together a detailed user guide and tutorial that takes you through the entire process, step by step, showing you how to create REST APIs, along with showing you how to get it working with the pre-built mgweb-conduit back-end Demonstrator/Example on IRIS, and how to add the wc-conduit front-end to the mg_web Server Appliance.
It's all very quick and simple to get it up and working, with lots of utility functions included in the kit that make it very simple to create your REST APIs, use JWTs, secure passwords etc. It's a different and alternative approach to using IRIS for REST APIs that you might find interesting.
Notice, by the way, the hefty performance penalty incurred by the SQL/Class option compared with the low-level ObjectScript functions ($extract and $translate).
go to post
No disrespect to what you've created, but I have to say I'm always amazed and dismayed at how complex the Java community always seem to manage to make even the simplest of tasks - Spring/Hibernate is a classic example of making a crazy mountain out of what should technically be a very simple mole-hill.
By comparison, take a look at mgweb-server: https://github.com/robtweed/mgweb-server and its underlying mg_web interface (https://github.com/chrisemunt/mg_web) for probably the thinnest (and therefore the most performant) and simplest way possible of delivering REST services using IRIS.
go to post
The simplest way is to use QEWD. It will save you a lot of time trying to sort out all the moving parts required.
Start here:
https://github.com/robtweed/qewd
and check this out: https://groups.google.com/g/enterprise-web-developer-community/c/HQK-THx...
Rob
go to post
Awaiting my app/repo to be approved and then I'll submit it to the competition...
Rob
go to post
We have two Open Source products that will look after JWTs for you in the ways you are asking about (ie REST services with IRIS):
- QEWD, if you want to implement everything at the back-end in Node.js / JavaScript
- mgweb-server if you want to use ObjectScript logic for your back-end logic
For QEWD and IRIS, see:
https://github.com/robtweed/qewd-starter-kit-iris-networked
In particular for REST services, see:
https://github.com/robtweed/qewd-starter-kit-iris-networked/blob/master/...
and specifically this section:
https://github.com/robtweed/qewd-starter-kit-iris-networked/blob/master/...
For mgweb-server, see:
https://github.com/robtweed/mgweb-server
specifically using with IRIS:
https://github.com/robtweed/mgweb-server/blob/master/IRIS.md
and within that document, this section on JWTs:
https://github.com/robtweed/mgweb-server/blob/master/IRIS.md#using-json-...
Rob
go to post
if you're a JavaScript/Node.js developer, you can use the QEWD-JSdb abstractions of IRIS:
- Document database
- Persistent JavaScript Objects
- Redis-like Lists
- Redis-like key/object store
- Persistent XML DOM (with XPath querying)
See: https://github.com/robtweed/qewd-starter-kit-iris-networked
Take the introductory tutorial:
https://github.com/robtweed/qewd-starter-kit-iris-networked/blob/master/...
and then delve into the other database models:
- https://github.com/robtweed/qewd-starter-kit-iris-networked/blob/master/...
https://github.com/robtweed/qewd-starter-kit-iris-networked/blob/master/...
https://github.com/robtweed/qewd-starter-kit-iris-networked/blob/master/...
A whole world of multi-model opportunities to explore for this competition!
go to post
If you're interested in trying out the mgweb-server Docker Container (aka mg_web Server Appliance) with an IRIS back-end (eg using the IRIS Community Edition Docker Container), I've put together a detailed user guide and tutorial that takes you through the entire process, step by step, showing you how to create REST APIs, along with showing you how to get it working with the pre-built mgweb-conduit back-end Demonstrator/Example on IRIS, and how to add the wc-conduit front-end to the mg_web Server Appliance.
It's all very quick and simple to get it up and working, with lots of utility functions included in the kit that make it very simple to create your REST APIs, use JWTs, secure passwords etc. It's a different and alternative approach to using IRIS for REST APIs that you might find interesting.
Why not take a look at:
https://github.com/robtweed/mgweb-server/blob/master/IRIS.md
go to post
Notice, by the way, the hefty performance penalty incurred by the SQL/Class option compared with the low-level ObjectScript functions ($extract and $translate).
go to post
Wot, read documentation?? ;-)
go to post
Results running IRIS Container on Raspberry Pi 4 (4Gb RAM):
$e() only 1.279893
$tr() 1.281999
$e()+$zd() 1.470656
SQL/class 66.405927
I didn't include the SQL/static in my test on the RPi.
Comparison with IRIS on a Windows 10 i7 based Intel NUC machine:
$e() only .14742
$tr() .185998
$e()+$zd() .182579
SQL/class 11.305143
Mind you, the NUC cost about 15 times that of the RPi :-)
Anyway, based on a combination of the performance and coolness of technique, the $tr() one gets my vote!
go to post
Wow, how have I not known this trick after all these years? :-)