ZNize Platform (Runtime, Framework, and SDK)

Multi-Tenant Runtime Architecture

Each organization (tenant) operates within an isolated tenant domain. The runtime enforces:

• Strict data isolation
• Domain-driven data engine
• Scoped execution context
• Tenant-level permission governance
• Independent lifecycle management

Tenants are equal and independent by design.

Modular Capability Assembly

The platform supports pluggable functional modules.

Application capabilities are not hard-coded. They are assembled. This enables:

• Feature-based activation
• Domain extensibility
• Controlled solution packaging
• Clean separation of concerns

Modules define business capabilities. The runtime composes them.

Model-Driven UI Framework

UI logical views are generated from domain model and application logic, and automatically bound to client environments.

• UI structures are not static templates.
• Logic views are runtime projections of domain logic.
• Logic views are bound to client platforms for user-interaction.

Logical view runtime binding ensures consistency across platforms without duplicating interface definitions.

Hierarchical Site Composition

Site hierarchies support inheritance and controlled overrides.

Tenants can build structured sites composed of:

• Pages with platform-neutral layout definitions
• Domain-integrated views with embedded interactive beans
• I18N internationalization

Customization is structured — not fragmented.

Hierarchical I18N Framework

Localization follows a structured resource inheritance model.

Resource resolution order:

• Site resource bundles
• Parent site resource bundles (hierarchical chain upward)
• Module resource bundles
• Core platform resource bundles

I18N is governed through layered resolution — eliminating duplication while preserving override control.

Transaction-Governed Domain Execution

Business objects execute within controlled transactional boundaries.

The runtime provides:

• Versioned optimistic locking
• State consistency enforcement
• Domain-level integrity control

This ensures reliable multi-party operations across isolated tenants.

Cross-Tenant Interaction

The platform provides a foundation for cross-tenant interaction, including data exchange and synchronization, process coordination, and collaboration across isolated tenant environments.

• Connected tenants collaborate on shared data.
• Data is exchanged and synchronized between tenants.
• Processes are coordinated and executed across tenants.

Cross-Tenant interaction is governed through domain rules and transactional updates to ensure data integrity and consistency.

Logical View–Aligned Test Automation

Client-driven automation leverages an API aligned with the platform’s logical view model.

Tests interact with business-level components such as pages, containers, dialogs, and domain objects instead of fragile web elements, ensuring stable and maintainable workflow validation across releases.

Subscription & Billing Infrastructure

Built-in subscription and billing module designed for multi-tenant environments.

• Tenant-level subscription management
• Flexible billing cycles (monthly / annual)
• Automated invoice generation
• Secure recurring payment processing
• Upgrade, downgrade, and renewal control

This ensures scalable commercial operations without external billing systems.