Unqork: No-Code Discipline for Managing Technical Debt

An Intellyx Brain Candy Update

Since we last covered Unqork in June 2020, the company has doubled down on its no-code messaging.

While other no-code vendors target nontechnical ‘citizen developers’ to build applications, Unqork goes after professional engineers – coders as well as other technical professionals who understand how to build performant enterprise applications.

Low-code vendors target this audience as well, with platforms that provide simplified, visual interfaces for most of the work of building applications, while allowing for the occasional need for hand-coding.

Unqork, in contrast, doesn’t allow hand-coding from within its platform. If engineers require custom capabilities (like custom integrations) that Unqork can’t provide, they must build them using other tools and then access them via their APIs from within Unqork.

The reason for this limitation: allowing hand-coding within a low-code platform opens a Pandora’s box of security and testing issues, and typically leads to added technical debt – messes that someone will have to clean up later.

With Unqork, you can’t make such messes. As a result, Unqork gives organizations the discipline to manage their technical debt, even if engineers find the limitations constraining. But that’s what discipline is all about.

Copyright © Intellyx LLC. Intellyx publishes the Cloud-Native Computing poster, advises companies on their digital transformation initiatives, and helps vendors communicate their agility stories. As of the time of writing, none of the organizations mentioned in this article is an Intellyx customer. To be considered for a Brain Candy article, email us at pr@intellyx.com.

SHARE THIS: