P
pedromarcerodriguez
Guest
Hi Torben, We have taken an approach to implement REST that diverges from the official route, but it might be a good fit for your purpose. Basically we have decided to take an approach based on node.js + MQ + ABL code (without even the requirement for and Appserver). The idea is we use nodejs (with restify) to define all REST resources and its methods available in our API (in fact this is generated dynamically from a swagger REST api document). Nodejs listen for those requests and deals with some of the middleware responsibility like first level of authentication, CORS, etc... Once that is passed it pushes a message to a MQ server (we use STOMP to connect the nodejs application to the MQ server so we can use almost any option available) with a JSON that includes all parameters corresponding to the request (headers, path, query parameters...). We also have some ABL listeners connected to the same MQ server (also using STOMP) and listening in that queue, once the message is received, there is a server program that executes all the logic required (this one would be very similar to the one you already have) and sends back to the queue the generated response. Then that response is passed back from the queue to the nodejs server that sends finally its response back to the client (mobile, web, ...). Hope that helps and introduces new ideas about how to approach this project. Regards,
Continue reading...
Continue reading...