Linx vs. Traditional Coding 

The development of backend applications – such as APIs, microservices, automations and integrations –  is time-consuming, complex and requires highly skilled developers.  Linx was designed to enable more developers to build backend applications and to shorten development time. 

Linx Traditional programming / Hand-coding
Getting Started

Install Plugins for the functionality you want to use (e.g. REST, Database). Installation is point and click.

Time spent: Minutes.

Select a framework to use and install the dependencies for any additional tech you want to use.

Time spent: Minutes to hours, depending on the technology selected, dependency compatibility and team conventions.


Understanding concepts

Use of Functions, Services and Types.

Ease of use: Easy for anybody with programming experience. It is challenging for non-programmers

Functions, Types and any concepts the framework or dependencies introduce.

Ease of use: Easy for programmers that’s used the selected tech before. Challenging for programmers that haven’t. Impossible for non-programmers.


Adding functionality
Drag Functions and Services from Plugins to create your own. Fill in properties and use editors to configure them.

Write code. Use the functions and types in the dependencies as building blocks.

Time spent: Hours to days, needs to deal with much more finely grained code, language, framework and dependency concerns


Hitting roadblocks
Use generic drag-and-drop Functions or code it. You need to code it.


Similar to most programming IDEs with the addition of Function and Service level debugging, e.g. write a Function and then immediately debug it. Mostly standardised across IDEs.



One-click directly from the IDE.

Time spent: Minutes.

Compile, install on host, run or set up continuous deployment.

Time spent: Hours.


Management, logging & metrics

Built-in as standard.

Time spent: Zero

Decide what tooling to use, build it into the code, set up the dependencies.

Time spent: Hours to days.