Corteza, the leading open-source low-code development platform just had the first release of its routing and processing gateway for HTTP requests and I’m here to tell you all about it.
As an ongoing effort, the plan for this routing subsystem has always been
- to minimize the effort in adding dynamic routes with any validation
- to be able to connect the routing possibilities with most of the Corteza subsystem
- to take the developer-first approach in modular architecture and data flow transparency
During our development processes and via a wide range of our client’s proposals and business requirements, we quickly noticed we outgrew the possibilities Corteza offered via it’s sink feature.
Sink allowed a Corteza developer to detect incoming HTTP requests on a fixed route via a generated signature wrapped in query parameters and provide the request to the automation scripts.
But having only one route with limited capabilities to validate query parameters, headers and have an overview of the amount of incoming data fell short.