Low Code: implementation and integration

Low-code is a development concept in which developers are responsible for creating a builder, a universal tool for solving complex and atypical tasks, from which all business requirements are then formed. Low-code accelerates the rollout of new functionality in a project and reduces development costs.

Low-code principles

Building a configurator
Visual modeling
Reduced development time

Comparing low-code with code-first development

Required resources for implementation: 2-3 managers (or business analysts) and 1-2 developers.
A development team (~7 people) and 1 manager (or business analyst).
Implementation time In the LCDP concept, development goes through 3 stages: task - builder - ready-made functionality.
Developers are not stuck with boring tasks, and in some cases the business gets changes faster. In the code-first paradigm, development follows the scheme "task - ready-made solution." The code-first cycle is longer, since every change goes through the usual development cycle.
User interfaces, business processes, data, and integrations in LCDP are visualized, allowing the business to formulate change requests more clearly and have a unambiguous, understandable view, provided naming conventions are followed.
In the code-first paradigm, code and user documentation are always separate.
Maintaining documentation requires extra effort, which does not eliminate duplicate content and narrative ambiguity.
LCDP is easier to hand over to operations thanks to its self-documenting nature and the simplicity of standardizing logging.
Handing over to operations requires a high level of development discipline from both the developers and the company's management.
Engineers do not handle repetitive routine tasks; their responsibility is reusable builder components.
This allows developers to focus on quality and the business to focus on value.
If developers are responsible for delivering and modifying the final value, engineers burn out and the business generates fewer changes.
Solving these problems requires significant investment in communication culture and complex processes.
The main focus is on building the builder or configuring an existing one, and the client can also make changes to the functionality directly.
This reduces development time and the cost of the final solution.
The cost of a ready-made solution is determined not only by development, but also by the need for further enhancements and technical support, which raise the price many times over.

Benefits of the low-code concept

Flexibility in tool selection The builder in low-code can be either an off-the-shelf solution or one that requires development. Functionality is then assembled on top of it. Less dependence on development Advanced business users can adjust existing functionality on their own, while the IT department develops only fundamentally new components and logic. The IT department is the brain, not the hands The IT department becomes not an executor, but a consultant and controller of the changes being made.

Our LCDP implementation cases

Enabled Polaris to easily launch new products on marketplaces and update product information in just a few clicks
Developed a target system integration architecture for a manufacturing enterprise.
Implemented ESB technology and launched 48 streams
Implemented a scalable service bus for ATIMO