Consolidating Multi-Region CMS Backends: Go, PHP, Architecture & Performance

1. Background

1) Current Situation Analysis

Multiple CMS back‑ends (1 domestic, 2 overseas).

Inconsistent features, development languages, development models, and data structures between domestic and overseas systems.

Three separate back‑ends mean developers and users must maintain two systems and master three different workflows.

Each system has its own advantages and optimization space, leading to duplicated optimization effort.

The above issues cause high maintenance and new‑feature development costs.

2) Involved Code

1) Domestic CMS code

cms.uuzu.com – CMS back‑end PHP logic.

cmsapi3.uuzu.com – Internal GO API for CMS.

uapi.uuzu.com – Internal common GO API of the Interaction Technology Department.

uapi.youzu.com – External common GO API (exposed to CMS, etc.).

common – Domestic shared common code.

go-common – GO shared common code.

2) Overseas CMS code

gtacms.gtarcade.com – New CMS back‑end PHP logic.

gtacms-api.gtarcade.com – New CMS external GO API (unfinished, no business use yet).

storage.gtarcade.com – Custom features; complex GOT data structures not supported by existing CMS.

gtacms-frontend – New CMS front‑end template code.

gta-common – Overseas shared common code.

cms.gtarcade.com – Legacy CMS back‑end PHP logic.

cms.api.gtarcade.com – Legacy CMS internal API.

common – Shared common code (same as domestic).

2. CMS Analysis

1) Domestic CMS functional modules (cms.uuzu.com)

HOME

System Settings: site management, editor templates, server IP.

Site Settings: layout, ads, custom settings, recommendations, fragments, CMS usage guide.

Content Management: articles, ads, custom content, albums, comments, replies, fragments, activities, recruitment, FAQ.

SEO Settings: site, layout, article, article expansion, friend links, keywords.

Scheduled generation & Varnish refresh.

System logs.

2) Domestic CMS architecture diagram (Node.js API & front‑back separation)

3) Overseas legacy CMS (cms.gtarcade.com)

The overseas legacy CMS back‑end is a copy of the domestic system with most features retained; only custom functions differ. It is no longer maintained, used only for the old official site.

4) Overseas new CMS functional modules

gtacms.gtarcade.com

Configuration Center: Game list.

System Management: Language, project, column, ad slots, statistics, operation logs.

Content Management: Articles, ads, site settings, language packs, FAQ, sidebars.

Operations Module: Pre‑registration, point tracking, gift‑code modules.

5) Overseas CMS architecture diagram (template engine)

6) Domestic CMS performance benchmark (PHP & Go)

1) PHP stress test report

2) Go stress test report

3. Summary and Recommendations

1) Optimization Plan (system choice, language & mode, key points, staffing)

System choice: Perform secondary development on the domestic CMS because it offers good performance, high flexibility, low migration effort, and minimal SEO impact.

Development language: Choose Go for its performance advantage; each instance can handle roughly 1500 concurrent requests.

Development mode: Adopt the overseas template‑engine approach to improve efficiency; use Go’s Jet template engine to keep language consistency.

Key development points:

UI optimization based on user research (friendlier operations, rationalized categories, reduced multilingual input).

Implement Go‑based template engine.

Refactor internal and external APIs; decouple the external UAPI.

Consolidate and optimize DB schema.

Separate domestic and overseas deployments; migrate the overseas new CMS back‑end (data layer, routing, rendering).

Staffing: 1 front‑end developer, 1 back‑end developer; estimated schedule 3 months (subject to review meeting).

2) Optimized Architecture Diagram (template engine & interface method)