There is no object–relational impedance mismatch in the platform - when a developer has to constantly choose between "fast" SQL queries and code in a "convenient" imperative language. Both approaches are so abstracted and combined that the boundary between them is almost non-existent. The developer always works with data in the same paradigm, and how and where all this work is done is entirely the responsibility of the platform itself.
The platform doesn't split the user interface into interactive forms and reports. Any form can contain both input and calculated data and can be displayed in a print (like a classic report) or interactive (editable) view. Accordingly, users can not only see the data they need to make a decision, but also immediately enter the decision they've made through the same UI.
The platform doesn't split business logic into server and client sides, which allows developers to request modal interaction with the user at any time. In this case, the platform automatically pauses the current action, sends a request to the user, and resumes the action as soon as the response is received.
When a certain action involves data processing for many objects at once, the platform tries, whenever possible, to perform this processing on the database server with a single query (i.e. for all objects at once). In this case, all generated queries are optimized as much as possible depending on the features of the database server.
The platform allows you to create event handlers for any changes in any data (even calculated data). The use of this mechanism allows you to significantly increase the modularity of the created solutions.
The platform allows you to materialize any existing indicators in the system at any time, add new tables or delete existing ones, or change the location of materialized indicators in these tables.
The platform allows you to create constraints on the values of any data (even calculated data). All such constraints (as well as events) are global, so an inexperienced user or developer cannot break them with an incorrect transaction.
All calculated data is automatically updated once the data it uses is changed. This rule applies always and everywhere, whether you're displaying interactive forms or simply accessing data inside the action being executed.
Supports any OS for which JVM is implemented, as well as the most popular relational databases.
The mapping of logic to the database is absolutely transparent, and the developer can totally control this process. No generated names or surrogate tables.
Any form can not only be shown to the user interactively or printed out, but also can be exported in most popular data formats (JSON, XML, CSV, XLS, DBF, etc.). This operation is symmetrical - you can also import data from a file in any of these formats back into the form. Both processes are absolutely declarative and use the same concepts as the UI, which greatly simplifies interaction with external systems.
Client-server communication at the physical level minimizes synchronous round-trip calls (i.e. each user action leads to a single - usually asynchronous - request/response pair). The desktop client also archives and encrypts all transferred data (when necessary). During client-server communication (via TCP/IP for the desktop client or HTTP for the Web client), the platform provides guarantee of delivery - it resends any lost requests and ensures that they are processed in the correct order. All these features help the platform run efficiently even on low-bandwidth, unstable, or high-latency communication channels.
The platform supports access to the system via the most common general-purpose application protocol (HTTP), and the access interface includes not only execution of some action (with automatic argument parsing), but also execution of lsFusion code (as when accessing SQL servers). In addition, the platform at the language level supports access to SQL servers, other lsFusion systems, any external systems via HTTP, etc. And, since the server itself is implemented as a Spring bean, you can manage its life cycle using a standard Spring IoC container. All these features allow you to use lsFusion not only as a fully-fledged development platform, but also as a database or even as a Java library.
The platform can safely roll back the state of the application server to the state at the start of any transaction. This allows you to use the native integrity tools of modern SQL servers, which not only significantly reduces labor costs and chances of human errors when developing a system for a highly concurrent environment, but also makes such a system much more scalable (provided that versioned DBMS are used).
All elements of the system, from events to form design, are written in the lsFusion language and stored in plain text files (without any shared repositories with an unknown structure). This allows you to use popular version control systems (Git, Subversion) and project-building tools (Maven, Gradle, built into IDEs) when working with projects. In addition, this approach simplifies the support and deployment of the system you develop, because it allows, first, using a simple text editor to view and, if necessary, quickly modify the logic, and second, easily identify any element in the system, by its file and line number in this file.
The platform allows you to group element names into namespaces and consider names in the same namespace as having higher priority when searching for elements. In most cases, you need to specify only the "short" name of the element you're searching, which makes the code more concise and readable. In addition, you can specify a class for each parameter in the code, and this class will also be taken into account during elements search (i.e. explicit typing is supported). This not only makes your code shorter and simpler, but also gives you early error detection, smart auto-completion, and lots of other useful features.
Intellij IDEA-based IDE with everything developers could ever need: usages search, code/error highlighting, smart auto-completion, quick jump to declarations, class structure, renaming of elements, usage tree, data change breakpoints, debugger, and many other features.
Do you want to create your own high-level operator, or maybe you just don't know how to generalize the logic, but want to reuse it? The platform provides full support for automatic code generation, both server-side and IDE-side.
The platform executes the imperative part of the system logic (i.e. everything related to data changes) on application servers and the declarative part (i.e. everything related to data calculations) on database servers. This separation simplifies the scaling of the system you develop and strengthens its fault tolerance due to the different nature of workload on these servers (e.g. using swap on an application server is much more dangerous than on a database server).
Since the application servers don't have any shared data, you can easily add as many of them as you need. In addition, the platform can transfer user data between database servers asynchronously, which, in turn, allows you to dynamically distribute the workload among them. For example, if data is written to the database (and thus ACID is needed), performing processing on the masters, and in other cases - on the least loaded slaves.
The extension technique allows developers to extend the functionality of one module in another (e.g. modify forms or classes created in another module). This mechanism makes the solutions you create much more modular.
The platform tries to perform all operations asynchronously whenever possible (i.e. return control to the user without waiting for the operation to complete). For example, such operations include most input operations and local event handling.
The platform supports inheritance (including multiple inheritance) and polymorphism (again, including multiple polymorphism). And, if inheritance isn't enough for you for whatever reason, the platform also provides an aggregation mechanism that, together with inheritance, allows you to implement almost any polymorphic logic.
The platform provides a lot of WYSIWYG features right out of the box. For example, the user can edit any data that he sees, do it at once for all visible objects (group editing), do copy-paste (including, for example, from Excel), merge / undo / save the changes made and do many other things that he is used to doing with Excel.
Within any string literal (e.g. an element caption or string constant) the platform allows to use IDs (in brackets) to which you can then set different texts for different languages. Accordingly, when this literal is accessed, the platform automatically localizes it depending on the language settings of the user, whose actions lead to this access.
The platform allows users to change any previously-entered data (e.g. to fix input errors) and only updates the data that is actually needed without thousands of related reversal operations, long reposting, or global database locks. In addition, the platform allows the simultaneous editing of the same data (e.g. the same document), which can be critical if you have a lot of data or need to enter it very quickly.
The platform provides a complete set of administration tools: interpreter - executes lsFusion code, process monitor - gets information about the current processes (such as call start time, stack, user, etc.), scheduler - executes action at specified times (including periodically), profiler - measures the performance of all actions executed for all/given users (builds a graph of calls, time division between the application server and the database server, etc.), messenger - for internal notifications/communication with users in the system, and numerous logs - connections, errors, etc.
When interacting with a user, the platform can display any data not only as single objects and lists, but also as trees, both flat ("nested") and recursive (e.g. classifiers). Moreover, if there is too much information, the platform allows you to group various form blocks into folders (tabs) and named collapsible containers. In this case, when the data is not visible to the user, it is not read/calculated (e.g. all lists are dynamic by default, i.e. only a limited number of objects are read initially, while the rest of them are read as the current object in the table is changed).
A flexible security policy allows you to define data access restrictions both at the form level and at the level of specific actions / indicators. In this case, the user will not only not see this data, but will not even be aware of its existence.
The open source code of the platform and IDE allows developers to study the behavior of the platform from the inside, create pull requests or custom builds, as well as license the developed solutions to be used in a strict security environment.
Users can customize any form, e.g. add custom selections and sorting rules, add / remove / reorder columns. Also, on any form the user can perform basic analysis - group the data he sees, calculate sums / maximums and other aggregates. In addition to the UI settings, users can also add logging, fill-in control, notifications about any data changes (including calculated data), etc.
The platform is licensed under LGPL v3, which allows you to freely use, distribute, and modify the platform as you wish.