Exploring Alternatives to Ingress and OpenROAD for Low-Code/No-Code Transition

[Sudip Roy]

Hi All,

I know this is the OR forum, and I may be asking an unconventional question, but in my organization, we are planning to move away from Ingress, OpenROAD apps, and the WebServer construct due to skillset limitations. Most importantly, we are aiming to adopt a low-code/no-code approach with easily available resources.

What are my options for a target stack? Personally, I love OpenROAD, and I understand that many functionalities would need to be completely rewritten since OpenROAD is very RAD-based.

Thank you! 

[Chris Clark]

I work for Actian, so take these thoughts with a pinch of salt 😉

On Wednesday, January 22, 2025 at 9:36:11 AM UTC-8 Sudip Roy wrote:

I know this is the OR forum, and I may be asking an unconventional question, but in my organization, we are planning to move away from Ingress, OpenROAD apps, and the WebServer construct due to skillset limitations. Most importantly, we are aiming to adopt a low-code/no-code approach with easily available resources.

I think it's going to depend greatly on the capabilities and features of your existing application, future goals, and budget.

Many existing OpenROAD applications are specific to the problem domain they were designed/implemented for, which don't always fit low/no-code solutions which typically have a golden-path use-case for ease of implementation but then either are difficult or (more commonly) don't support straying away from that golden path.

If this is a skillset issue, I can recommend taking a look at the  Actian Academy (link) training courses, when taking the online/self-lead versions there is no additional cost. Actian Academy courses are included as part of the subscription for Ingres and OpenROAD and are the same content/material as the in-person training sessions that the training department offer. I know of one Actian partner that hires smart graduates straight out of college/university and has them up and running within a week to contribute to development projects with zero prior experience of OpenROAD or Ingres. That's been very cost effective for them.

 

What are my options for a target stack? Personally, I love OpenROAD, and I understand that many functionalities would need to be completely rewritten since OpenROAD is very RAD-based.

HCL would love to talk to you about HCL Volt MX Platform Features - HCLSoftware 😉

I would recommend taking stock of the functionality you have. It is common for OpenROAD custom applications to be bespoke CRM and/or ERP systems, you may find an off the shelf tool might hit some of the checkboxes you need. It is my observation that most OpenROAD applications were written because they needed functionality outside of core CRM/ERP functionality and needed a Turing complete language to perform all the require processing. One place to take a look at is multi-statement transaction support, this is trivial in OpenROAD (I'm willing to bet a Mars bar your applications are making use of these) which tend to be poorly supported (or not at-all) in low/no-code solutions.

I'm happy to chat with you in more detail if you have questions.

Chris

[Paul A.]

Memory lane - for some