Architectural Principles and System Mechanisms

Home / Support / Manuals / Administrator Guide /

Architectural Principles and System Mechanisms

Design Philosophy of the Framework

NET Genium is not merely a low-code tool, but an application operating system that:

  • unifies work with data, users, permissions, and history,
  • ensures transactional safety without the need to write application code,
  • strictly separates application behavior configuration from program code.

The core principle is:

The administrator defines the structure and behavior of the application; the runtime ensures technical execution.

Automatically Managed Database Layers

Form-Level Database Abstraction

Each edit form:

  • represents exactly one database table,
  • owns its own record lifecycle (create / update / delete),
  • has automatically generated history.

The administrator:

  • never modifies the database structure manually,
  • works exclusively at the level of forms and UI controls.

This guarantees:

  • database consistency,
  • backward compatibility during upgrades,
  • the possibility of automated migrations.

System Columns as Carriers of Application Logic

Columns such as id, userid, pid, pform, system are not technical details, but the foundation of application logic:

  • userid – ownership and editability
  • pid + pform – tree and hierarchical relationships
  • system – protection of critical records

This makes it possible to:

  • control permissions without explicit ACL tables,
  • create hierarchies without join tables,
  • apply uniform rules across the entire system.

Ownership and Co-Ownership as a Security Model

NET Genium uses a data-oriented security model, not a traditional role-based model known from classical applications.

The Record as the Primary Security Unit

Permissions are not defined only:

  • at the form level, or
  • at the table level,

but at the level of an individual database record.

This enables:

  • shared working records,
  • individual responsibility,
  • a built-in audit trail without additional configuration.

Co-Ownership as a Tool for Team Collaboration

Co-ownership:

  • is not an attribute of the record,
  • is a property of the form.

This ensures that:

  • security rules remain consistent,
  • permission fragmentation does not occur,
  • changes in policy take effect immediately.

Script as a Deterministic Process Language

Script Is Not a Programming Language

The script:

  • does not contain blocks,
  • does not contain local scopes,
  • does not contain exceptions in the programming-language sense.

It is:

a deterministic process notation over data and events.

Script as a Transactional Orchestrator

Each script:

  • runs within the context of a single database transaction,
  • either completes fully or performs no changes at all,
  • cannot partially persist data.

This guarantees:

  • a consistent database state,
  • predictable behavior,
  • safe execution even of complex processes.

Separation of Runtime Responsibilities

NET Genium strictly separates:

  • what should happen (configuration, script, query),
  • how it is executed (runtime, engine, C# code).

As a result:

  • administrators focus on logic, not implementation,
  • external function developers focus on performance and exceptions, not application context,
  • framework updates do not require application changes.

Concept of Synchronization and Distributed Installations

Synchronization is not database replication, but:

the transfer of change operations.

Thanks to this approach:

  • multiple active instances (multiple master) are possible,
  • conflicts at the database engine level are avoided,
  • operational, mobile, and archival environments can be separated.

Configuration Files as System Switches

Configuration files:

  • are not application settings,
  • but controls of runtime behavior.

Their existence has a binary meaning:

  • security modes,
  • operational limitations,
  • diagnostic behavior.

This approach enables:

  • behavior changes without database restarts,
  • clear auditability,
  • separation of operations from application configuration.

Intended Audience

This document is intended for:

  • NET Genium system architects,
  • administrators designing large-scale applications,
  • developers of external functions,
  • technical support and partner onboarding.

It is not intended for:

  • regular administrators,
  • end users,
  • marketing purposes.

Final Summary

NET Genium is designed as a stable, deterministic, and auditable application framework in which:

  • data is primary,
  • processes are configurable,
  • the runtime ensures security and consistency.

This guide serves as a bridge between documentation explaining "how to use the system" and knowledge explaining "how the system works".