Xinchuang Compression Software: Domestic Compatibility Solution

BLUF: For Xinchuang (Information Technology Application Innovation) environments, we recommend SmartSlim Enterprise/Server, which has completed full-stack Xinchuang adaptation — OS supports Kylin and UOS, CPU supports Phytium and Kunpeng, database supports DM and Kingbase, and middleware supports TongTech. This article details the Xinchuang ecosystem compatibility matrix, SmartSlim's adaptation solution, a government Xinchuang deployment case study, and a comparison of Xinchuang vs. traditional environments.

If you're not yet familiar with compliance requirements for government document compression, we recommend first reading Government OA System Document Compression: OFD/PDF Batch Processing Solution.

1. Xinchuang Ecosystem Compatibility Matrix

The core of Xinchuang environments is "domestic substitution" — using domestic products across the full stack of OS, CPU, database, and middleware. Compression software must complete compatibility adaptation at each layer to run on this full-stack domestic environment. The table below shows the compatibility requirements for each layer of the Xinchuang ecosystem.

Tech Stack Layer	Xinchuang Products	Foreign Equivalents	Adaptation Requirements
Operating System	Kylin, UOS	Windows/RedHat	Native Linux execution, RPM/DEB packages
CPU Architecture	Phytium, Kunpeng	Intel Xeon/AMD	ARM64 instruction set compilation
Database	DM, Kingbase	Oracle/MySQL	SQL dialect compatibility, ORM adaptation
Middleware	TongTech	Tomcat/Nginx	Application container adaptation
Browser	Qi-Anxin Browser	Chrome/Edge	Frontend JS compatibility

Xinchuang adaptation isn't as simple as "can run on Linux." Phytium and Kunpeng are both ARM64 architecture, but have different instruction set optimization points; DM and Kingbase both comply with SQL standards, but differ in stored procedure syntax and driver interfaces; TongTech middleware and Tomcat have different deployment configurations. Each layer requires targeted testing and adaptation — none can be skipped.

SmartSlim's adaptation status in Xinchuang environments is as follows.

Xinchuang Component	Specific Version	Adaptation Status	Verification Method
Kylin	V10 SP1/SP2/SP3	Certified	Compatibility testing + Xinchuang catalog
UOS	V20 1020/1050	Certified	Compatibility testing + Xinchuang catalog
Phytium CPU	D2000/S2500/FT2000	Native support	linux-arm64 precompiled
Kunpeng CPU	920/930	Native support	linux-arm64 precompiled
DM Database	DM8	Adapted	SQLAlchemy dialect configuration
Kingbase	KES V8	Adapted	PostgreSQL protocol compatibility
TongTech Middleware	TongWeb 7.0	Adapted	WAR package deployment verification

SmartSlim provides 6 platform precompiled versions, with linux-arm64 covering both Phytium and Kunpeng domestic CPUs. The Rust compression engine exports dynamic libraries (.so) through standard C ABI, running natively on domestic CPUs without emulation layers, with zero performance loss. DM and Kingbase adaptation is completed through the SQLAlchemy ORM layer, requiring no business code changes.

2. SmartSlim Xinchuang Adaptation Solution

SmartSlim's adaptation solution for Xinchuang environments is explained by product form, with Server and Enterprise editions having different adaptation priorities.

Product Form	Xinchuang Adaptation Scope	Deployment Method	Typical Scenario
Desktop	Kylin/UOS Desktop	DEB/RPM package installation	Personal office terminal
Server	Kylin/UOS Server + Phytium/Kunpeng	Docker/systemd	Single-machine compression service
Enterprise	Full-stack Xinchuang (OS+CPU+DB+middleware)	Docker Compose/K8s	Enterprise-grade batch compression
SDK	linux-arm64 dynamic library	.so integration	Xinchuang application embedding

Enterprise edition's Xinchuang adaptation is the most complex because it involves database and middleware replacement. The table below shows the adaptation checklist for migrating Enterprise edition from traditional to Xinchuang environments.

Component	Traditional Environment	Xinchuang Environment	Adaptation Work
Database	MySQL 8.0	DM8/Kingbase KES	SQLAlchemy dialect configuration + DDL script conversion
Cache	Redis 7	Redis (Xinchuang edition)	No changes needed
Object Storage	MinIO	MinIO (Xinchuang edition)	No changes needed
Message Queue	Celery+Redis	Celery+Redis (Xinchuang edition)	No changes needed
Web Service	Uvicorn	TongTech TongWeb	WAR package repackaging
Compression Engine	Rust .so	Rust .so (arm64)	Replace precompiled library

The core adaptation work focuses on database and web service. Database migration from MySQL to DM/Kingbase is completed through SQLAlchemy ORM layer dialect configuration, with table structures regenerated using DM/Kingbase DDL syntax. Web service migration from Uvicorn to TongTech TongWeb requires packaging the FastAPI application as a WAR for deployment. Other components (Redis, MinIO, Celery) are compatible between Xinchuang and open source versions, requiring no changes.

3. Case Study: Government Xinchuang Environment Deployment

A municipal government department needed to deploy a document compression service in a Xinchuang environment for batch compression and archiving of OFD/PDF documents generated by the OA system. Environment configuration: Kylin V10 SP2 Server + Phytium S2500 CPU (64-core) + DM8 database + TongTech TongWeb 7.0 middleware.

Deployment Environment Configuration:

Configuration Item	Specification	Description
Operating System	Kylin V10 SP2	Xinchuang catalog certified version
CPU	Phytium S2500 64-core	ARM64 architecture
Memory	128GB DDR4
Storage	2TB NVMe SSD	Local storage, no external network
Database	DM8	Replaces MySQL
Middleware	TongTech TongWeb 7.0	Replaces Tomcat
Deployment Form	Docker Compose	9-service container orchestration
Network	Government intranet	Physical isolation, data stays on-premises

Deployment Process and Time:

Step	Operation	Time	Key Verification Points
1	Environment check	30 min	OS version/CPU architecture/database instance
2	Container image pull	45 min	arm64 image integrity verification
3	Database adaptation	3 hours	DDL script conversion + data migration
4	Middleware deployment	1 hour	TongWeb WAR package deployment
5	Compression engine replacement	15 min	arm64 .so library replacement
6	Functional testing	2 hours	OFD/PDF compression + audit logging
7	Performance testing	1 hour	12 concurrent stability verification

Results: Total deployment took approximately 8 hours (including 3 hours for database adaptation), and the system ran stably after deployment. Testing compression of 1000 OFD documents (totaling 8GB) took 18 minutes with a 76% compression ratio, and compression logs completely recorded operators and file hashes. The Phytium S2500's ARM64 performance was comparable to equivalent Intel Xeon, with the Rust compression engine's native ARM64 compilation showing zero performance loss. The entire deployment was conducted over the intranet, meeting government data security requirements.

4. Xinchuang vs. Traditional Environment Comparison

Xinchuang environments differ from traditional x86+Windows/RedHat environments in multiple dimensions. The table below compares their performance in compression scenarios.

Comparison Dimension	Traditional Environment	Xinchuang Environment	Difference Description
Operating System	Windows/RedHat	Kylin/UOS	Xinchuang OS is based on Linux kernel, CLI-friendly
CPU Architecture	x86_64	ARM64 (Phytium/Kunpeng)	Requires arm64 precompiled version
Database	MySQL/Oracle	DM/Kingbase	SQL dialect needs adaptation
Deployment Method	Docker/K8s	Docker/K8s (Xinchuang edition)	Containerization approach is consistent
Compression Performance	Baseline	Equivalent	Rust engine performance is consistent across architectures
Compliance Certification	None	Xinchuang catalog certification	Classified units must have Xinchuang certification
Data Security	Requires additional measures	Physical isolation + localization	Xinchuang environment has higher security baseline

Key conclusion: Xinchuang environment compression performance is on par with traditional environments, with the Rust compression engine's cross-platform nature ensuring consistent performance between ARM64 and x86_64. Differences are mainly in deployment adaptation (database, middleware replacement) and compliance certification. Functionally, the two are completely equivalent — SmartSlim's format support, compression ratio, and batch processing capabilities are identical in Xinchuang and traditional environments.

Scenario recommendations for Xinchuang environments are shown below.

Use Case	Recommended Product	Deployment Method	Compliance Points
Government Terminal Office	SmartSlim Desktop	DEB/RPM installation	Xinchuang catalog certified version
Government Document Archiving	Server	Docker single service	Local compression + audit logging
Classified Unit Batch	Enterprise private deployment	Physical server on-site deployment	Physical isolation + MLPS 2.0
Xinchuang application embedding	SDK (arm64)	.so dynamic library integration	Native ARM64 compilation
SOE Data Archiving	Enterprise Docker	Docker Compose	Full-stack Xinchuang adaptation

For compliance requirements for enterprise file processing, refer to Enterprise File Processing Compliance Guide under the Data Security Law. If you need to compare compression tool selection dimensions, refer to File Compression Tool Selection Guide: 7-Dimension Evaluation.

5. Frequently Asked Questions (FAQ)

Q1: What compression software to use in Xinchuang environments?

We recommend SmartSlim Enterprise/Server, which has completed full-stack Xinchuang adaptation: OS supports Kylin and UOS, CPU supports Phytium and Kunpeng, database supports DM and Kingbase, middleware supports TongTech. Foreign software like 7-Zip can run on Linux but lacks Xinchuang certification — classified units must use domestically certified software. SmartSlim is listed in the Xinchuang catalog and is qualified for government and classified scenario deployment.

Q2: Does SmartSlim support Kylin and UOS systems?

Yes. SmartSlim provides linux-x64 and linux-arm64 precompiled versions, having completed compatibility testing and Xinchuang certification on Kylin V10 and UOS V20. Server edition supports systemd/supervisor/Docker deployment, and Enterprise edition supports Docker Compose and K8s deployment on Kylin/UOS. The Rust compression engine's C ABI dynamic library (.so) natively supports domestic Linux distributions without emulation layers.

Q3: What are the differences between Xinchuang and foreign compression software?

Three core differences: first, certification compliance — Xinchuang software must pass national Xinchuang catalog certification, which foreign software lacks, making it prohibited for classified units; second, ecosystem adaptation — Xinchuang software natively supports domestic CPU/OS/database, while foreign software may have compatibility issues; third, security and controllability — Xinchuang software has controllable source code and localized data, while foreign software carries supply chain risks. In terms of functionality, both have similar compression capabilities, with SmartSlim's Rust engine achieving compression ratios comparable to 7-Zip, but with more comprehensive format support (10 categories, 40+ formats vs. 7-Zip's archiving).

Q4: How to deploy compression solutions in Xinchuang environments?

Three-step deployment: first, environment preparation — confirm Kylin/UOS OS version, Phytium/Kunpeng CPU architecture, and DM/Kingbase database instance; second, software installation — Server edition uses RPM/DEB packages or Docker images, Enterprise edition uses Docker Compose to orchestrate 9 service containers; third, data migration — migrate original MySQL data to DM/Kingbase and configure the Xinchuang middleware TongTech. Government environments require physical server on-site deployment with fully intranet-based operations, taking approximately 2–3 days. In testing, a government environment deployment was completed in 8 hours.

Summary

Xinchuang compression software selection centers on "full-stack adaptation + certification compliance." SmartSlim has completed full-stack Xinchuang adaptation from OS (Kylin/UOS) to CPU (Phytium/Kunpeng) to database (DM/Kingbase) to middleware (TongTech), and is listed in the Xinchuang catalog. In testing, a government Xinchuang environment deployment was completed in 8 hours, with compression performance on par with traditional x86 environments. The Rust compression engine's cross-architecture nature ensures native ARM64 execution with zero performance loss.

Xinchuang isn't about "just being able to run" — it's the trinity of "full-stack domestic, certified compliance, security and controllability." Classified units must choose domestically certified software; foreign software, even if it can run on Linux, doesn't meet compliance requirements. Choosing the right Xinchuang compression solution is both a compliance baseline and a fundamental guarantee of data security.