Component Collaboration

LinaPro components collaborate around three main threads:

Thread	Description
API contracts	The core framework and plugins declare APIs; the workspace consumes them and supports debugging through the API documentation
Plugin governance	Plugin manifests drive installation, enablement, upgrades, disablement, uninstallation, menu projection, permission resources, and lifecycle callbacks
Runtime coordination	The core framework handles authentication, authorization, tenant context, configuration, scheduling, cache revision, and cluster coordination

Through these components, LinaPro brings the backend core framework, frontend workspace, business plugins, and deployment runtime under a unified governance model. Developers can extend business capabilities with plugins while keeping the core framework stable, and get a complete management experience through the built-in admin workspace.

Related Topics

📄️Core Framework Service

A component-level guide to the LinaPro core framework service lina-core — covering API contracts, governance services, runtime configuration, API documentation aggregation, scheduling, internationalization, multi-tenant foundation, plugin runtime, cluster coordination, and health probes, and how the core framework serves as a stable foundation for the workspace, source plugins, and WASM dynamic plugins.

📄️Built-in Admin Workspace

A component-level guide to the LinaPro built-in admin workspace, lina-vben — how it serves as the standard frontend consumer of the core framework service and plugin system, covering access control, system settings, job scheduling, multi-tenant management, plugin governance, developer center, and dynamic plugin pages, while maintaining consistency with backend API contracts, menu permissions, and I18N resources.

🗃Dual-Mode Plugin System

3 items

📄️Native Distributed Architecture

From a component design perspective, this page explains the native distributed architecture of LinaPro — how to switch between single-node and cluster mode, the Redis coordinator, leader election, node responsibilities, cache revision, distributed locks, key-value cache, scheduled task execution scope, and the horizontal scaling process — helping developers understand how business code can scale to multi-node deployment with zero modifications.

📄️Service Configuration

A component-level guide to LinaPro core framework service configuration — how config.yaml drives HTTP server, logging, database, JWT authentication, sessions, monitoring, health probes, scheduling, internationalization, cluster coordination, file uploads, and plugin governance, with production deployment recommendations.

📄️OpenAPI Reference

From a component design perspective, this page explains how LinaPro aggregates API documentation — the core framework, source plugins, and WASM dynamic plugins are unified into a single OpenAPI document through g.Meta contracts, permission tags, API doc i18n resources, the in-workspace developer center debugging page, and third-party tool import.

📄️Native Multi-Tenancy

A component-level guide to LinaPro multi-tenancy — how the core framework bizctx, TenantFilterService, tenant_id filtering seam, default platform tenant, official multi-tenant source plugin, tenant impersonation, plugin multi-tenant manifest fields, and the current Pool shared-database model work together.

📄️Scheduled Tasks

A component-level guide to the LinaPro persistent scheduled task system — task types, cron expressions, task groups, execution logs, built-in tasks, source plugin and dynamic plugin task declarations, master_only and all_node execution scopes, singleton and parallel concurrency strategies, and cluster scheduling behavior.

📄️Framework-Level Internationalization

A component-level guide to the LinaPro I18N internationalization runtime — how core framework language packs, plugin language packs, dynamic plugin language resources, API documentation translations, runtime caching, locale configuration, and frontend language switching work together, and what resource boundaries teams must maintain when adding new languages.