OrangeForms Low-Code Platform

The OrangeForms import process is designed for high runtime performance through four key stages:

1. Parsing: Uses SAX mode to read Excel files efficiently.
2. Translation: Uses a general reflection-based approach for reverse dictionary translation (e.g., converting a text value like 'Grade 2' to its corresponding dictionary ID 2).
3. Validation: Implements batch validation to minimize database interactions (e.g., avoiding individual queries for every dictionary field across thousands of rows).
4. Insertion: Uses small-batch insertion to improve performance and prevent memory or timeout issues associated with oversized single transactions.

The multi-tenant global dictionary system manages lookup data (e.g., grades, subjects) using a combination of database tables and Redis caching. It distinguishes between two types of dictionaries:

1. Tenant Public Dictionaries: Shared across all tenants. Data is maintained centrally in the tenant management backend; all tenants see the same values.
2. Tenant Non-Public Dictionaries: Tenant-specific. Initial data is provided by the system, but each tenant has its own copy identified by tenant_id. Tenant administrators can modify these values without affecting other tenants.

Caching Strategy: All multi-tenant global dictionary data is fully cached in Redis. The cache keys incorporate the tenant_id and dictionary_code to ensure isolation between different tenants' dictionary values.

OrangeForms handles applications based on the project architecture:

• Monolithic and Microservice Projects: By default, there is only one application.
• Multi-tenant Projects: Two applications are created during project initialization: the "Tenant Management Application" (租户管理应用) and the "Tenant Operation Application" (租户运营应用), allowing for separate business configurations.

In the OrangeForms generator, multi-tenant projects are initialized with a simplified architecture consisting of two primary database connections:

• Tenant Management (tenant-admin): Used by the management backend.
• Tenant Operation: In the default simplified setup, the common business database (tenant-common) and the business database (tenant-business) are merged into one connection.

Tenant Sync Service (tenant-sync): This service synchronizes configuration data (menus, permissions, dictionaries, etc.) from the management database to the business databases. It requires configuration for tenant-admin and tenant-common. Individual tenant business database connections are handled via a dynamic data source mechanism and do not need to be hardcoded in the configuration file.