Wir helfen Unternehmen seit 17 Jahren,
bessere Software zu finden
Was ist Linx?
Ein Low-Code-Entwicklungstool für IT-Profis und Business-Analysten zur Entwicklung umfangreicher, auf Geschäftsprozesse ausgerichteter Anwendungen mit technisch komplexen Aufgaben und mehreren Schritten, alles ohne Programmierung. Linx ist Zuverlässig und skalierbar und damit das perfekte Werkzeug für die durchgängige Prozessmodellierung, -ausführung, -prüfung und -integration, die Entwicklungszeit wird drastisch reduziert und geschäftskritische sich wiederholende Aufgaben werden eliminiert.
Wer verwendet Linx?
Devops, Entwickler, Datenbankadministratoren, IT-Manager, IT-Support, Citizen Developer, Technisch gesinnte Besitzer von Geschäftseinheiten
Du bist nicht sicher, ob Linx das Richtige ist?
Mit einer beliebten Alternative vergleichen
Linx
Bewertungen über Linx
Excellent support from start to finish
Kommentare: Extremely functional piece of data connection puzzle
Vorteile:
Very helpful in providing access to developer partners to implement a complete solution, and provide customer access after for easy maintenance.
Nachteile:
There's nothing I don't like, but the only con is that it doesn't have the most user-friendly interface, relative to competitors, but since those competitors cost more than 50 times as much, there's no real competition when all is considered.
In Betracht gezogene Alternativen:
Linx, ease of use and the best price for integration
Kommentare: We choose Linx to solve our integration problems to connect our applications with many systems
Vorteile:
Linx Designer, and Linx Server, are easy to use and we use Linx to develop our integration platforms that are connected to many systems, all easily and effectively
Nachteile:
Version Control will be vital / could be improved in Linx because we need that to control any changes to applications within the software development lifecycle
Is Linx for you?
Kommentare: Overall, Linx's current model is lacking in too many areas which are important to developers who need to deploy applications quickly across multiple platforms. Linx Server should not have a place in the build/deployment stage. This alone limits my available options for building/deploying where I want to for the most efficiency. I shouldn't have to change my approach to developing application to ensure that Linx fits squarely.
Vorteile:
My initial assessment is unbiased, the application is easy to deploy. The Linx IDE and Linx Server both maintained a very reasonable memory footprint. I didn't have any lag during build or deployment phases.
Nachteile:
My primary concern is dependency issues that involve deploying to Linx Server. My secondary issue is the lack of importing other projects files from other popular ide's. Not having direct Visual Studio support in regard to syncing projects is a major affair. The Linx "bundle" (ide, and server) just doesn't extend the type of functionality need for today's developer. If the deployment model is changed to include other platforms, Linx could justify itself as a potential major player. As a developer, we know beyond question that build/deployment platforms are a matter of taste or technique. That being said, this requires a great deal of flexibility when we decide to utilize a particular tool for software engineering. Linx does have a rapid build model in place that is competitive. However, do not neglect the need for sound logical principles during getting/setting datatypes. The Linx is not so "out-of-the-box" in the foregoing, very little is done by Linx behind the scenes to either generate common sql scripting from scratch or a template (which are non-existent). From my experience, true rapid application development must have drag-and-drop features. A designer view is required to implement this feature. Unfortunately, Linx fails here also.
Rapid, Easy Backend Development... Linx
Kommentare: I have loved using Linx and look forward to exploring more with it and its various plugins.
Vorteile:
I started working out of university at the beginning of the year. I got a job at a great company that used Linx software for backend development and I am extremely impressed. In comparison to the complexities of other coding languages... syntax and spelling errors and that is before you have even started to contemplate deployment; Linx makes coding a breeze to implement and deploy your logic. Being my first low code software tool, I was worried that it may be restrictive in what you can do, however, I have since developed multiple processes and API being used in the financial services industry and have never felt Linx to limit my imagination in terms of what can be achieved. Furthermore, when it comes to debugging, Linx allows for simple step-throughs as it should be with software programs, and deployment is then as easy as uploading a file (actually easier with the new update). The low-code, drag-and-drop nature of the application accommodates making minimal mistakes and allows for rapid development. Linx is thus a tool I would recommend to anyone needing backend software solutions.
Nachteile:
I am extremely impressed with Linx and how it works. For the last just under a year I have not found to be limited in any way and am continuously impressed with what can be achieved with the program. I look forward to using it more and finding a con (if possible).
Flexible systems integration toolkit
Kommentare: Automated systems integration
Vorteile:
As a consulting firm helping our clients solve complex systems integration challenges we have found Linx to be an excellent toolkit that includes an environment that supports the development of the collecting of data from multiple source types, transforming that data as required using multiple techniques, then delivering the results to multiple target systems. It also thereafter supports the continuous automated processing of the results of the development work as an unattended server service. As a result we have solved many different systems integration challenges including as our clients needs have evolved.
Nachteile:
The Help functionality in version 4 is limited, making the toolkit less of a self sufficient solution that it might otherwise be. However the level of support means this is not a practical problem, which in any case is due to be addressed in version 5.