4.5 C
New York
Wednesday, November 30, 2022

What IT pros need to know about low-code limitations – TechTarget

Low-code is a development approach that relies on automation and abstraction to simplify the software creation process — at the cost of the customization available with traditional programming. But do low-code’s limitations make it a bad strategy for enterprise IT?
Low-code development is based on tabular specifications or drag-and-drop features, which limit what low-code applications can do. In most cases, low-code has a specific set of template applications, the most common of which is select-and-report.
Because low-code platforms make software development easier, so-called citizen developers can use them with no programming training or skills. However, professional developers can also use low-code tools, though they don’t offer the full spectrum of programming techniques available with true programming languages.
The broad applicability of low-code has three distinct adoption models:
Low-code has limitations related to development and ongoing application use.
The most common low-code limitation is a presumptive application structure. Almost all low-code tools have a limited number of application types, such as select-and-report, summarize-and-report or match-and-process. The low-code developer can then fill in details for the selected model. While this takes much of the routine file and record handling out of the developer’s hands and reduces programming time, it also constrains the application’s capabilities.
A related limitation is reliance on drag-and-drop or tabular functionality specifications. Low-code relies on functions rather than instructions. These can sometimes be applied by dragging a function block into place in a flow diagram or specifying actions in tabular form — a popular report-and-display creation strategy. While some tools enable programmers to create functions for use by low-code developers, the lack of general programming language capabilities limits what can be done with the data.
In addition, low-code applications sometimes require major changes to accommodate what appear to be minor refinements in requirements. This is true when a different application model is mandated because of a specification change. In some extreme cases, a seemingly minor change could be impossible to support with a low-code tool because there is no corresponding application model or code feature to support it.
Poor application performance and resource use is a common complaint about low-code. Low-code application performance is almost always noticeably poorer than software developed in a true programming language.
This problem is most acute when the low-code application must handle a large number of records, is run regularly over a long period of time or both. This means that enterprises running low-code applications in the cloud can be hit with unexpectedly high cloud charges.
Low-code development can also lead to errors not caught by the package and that then go undetected long enough to waste time and resources. For example, a low-code select-and-report application might have criteria that select nothing or create invalid data due to a programming error. Most low-code products do not impose testing and release discipline on developers, and citizen developers don’t always understand how to apply these disciplines on their own.
The first model for low-code adoption — uncontrolled citizen developer involvement with low-code tools — is risky, as it’s likely to be affected by all the limitations listed above. The second model — IT-moderated citizen development based on low-code — can readily overcome all those limitations.
The key is for software professionals to qualify, audit and support low-coders. Consulting firm CIMI Corporation’s research found that enterprises say a single professional can support between 30 and 100 low-coders. This more than justifies the investment in resources through improved project turnaround and a better relationship between IT and line-of-business organizations.
The third model — use of low-code by IT professionals — is a bit more problematic. Professional programmers can, of course, create a traditional application using a modern programming language, but adopting low-code can speed up simple application development. Given the limitations of low-code, however, this might not be enough of a benefit to merit adoption.
Development organizations’ views are mixed on this issue. About half believe that it’s better to use low-code tools to free up developer time, whereas the other half think that developers should use “real” programming tools and techniques, according to CIMI Corporation’s research.
Because there are merits to both positions, it’s often best for enterprises considering either the first or third low-code model to instead converge on the second. Too much reliance on developers can be as bad as too little. If the goal is to speed up simple application development and save developer resources, shift to a model where line-of-business organizations with proper IT support can develop their own low-code applications.
What is the future of low-code app development?
4 low-code best practices to streamline adoption
Software Delivery Shield reduces security risks across the development pipeline — but it also increases developer productivity, …
From simplified test setup to enhanced isolation, Docker containers offer a range of advantages to QA engineers. Containers also …
The Copenhagen Pledge on Tech for Democracy highlights how tech can crumble or shore up democracy and human rights. But it lacks …
Developers who work with microservices may find the concept familiar, but cell-based architecture takes its own spin on …
Micronaut 3.0’s updates to annotation changes bean management and injections may intrigue developers working on coding paths and …
Application modernization should be at the top of an enterprise’s to-do list for five reasons, including security concerns, …
Google Cloud wants to shift workloads and applications from banks, healthcare and other industries into the cloud with a new …
One of the first steps in a cloud migration is to choose a data transfer model. There are two options to consider — online and …
A KPMG survey of 1,000 executives found that two-thirds were reevaluating cloud spending after failing to achieve a significant …
Many organizations struggle to manage their vast collection of AWS accounts, but Control Tower can help. The service automates …
There are several important variables within the Amazon EKS pricing model. Dig into the numbers to ensure you deploy the service …
AWS users face a choice when deploying Kubernetes: run it themselves on EC2 or let Amazon do the heavy lifting with EKS. See …
Want to prove your knowledge of Scrum? Tackle this 10-question Scrum introduction quiz and see how well you know the Scrum …
Here’s a tough 10 question Scrum Master quiz to test you on how well you know the responsibilities of this important Scrum role …
From System.in to the Scanner class, there are many ways to read user input into your Java programs. Find out which Java user …
File server reporting within File Server Resource Manager can help admins identify problems and then troubleshoot Windows servers…
Administrators who manage many users can go one step further toward streamlining license assignments by taking advantage of a new…
ServiceNow doubled down on its commitment to take the complexity out of digital transformation projects with a new version of its…
All Rights Reserved, Copyright 2016 – 2022, TechTarget

Privacy Policy
Cookie Preferences
Do Not Sell My Personal Info

source

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles