Mobile Development 8 min read

Case Study: Shenzhen Airport Mini‑Program Built with Tencent Cloud OneID System

Shenzhen Airport’s new mini‑program, launched with Tencent Cloud’s OneID system, unifies passenger identity across outbound, inbound, transfer and pick‑up scenarios to deliver 31 personalized services such as indoor navigation and luggage tracking, while leveraging serverless cloud development, two‑level caching, built‑in logging, multi‑environment management, and GDPR‑compliant data security to dramatically shorten development cycles and eliminate traditional server deployment.

Tencent Cloud Developer
Tencent Cloud Developer
Tencent Cloud Developer
Case Study: Shenzhen Airport Mini‑Program Built with Tencent Cloud OneID System

On December 10, 2019, during the 2019 Civil Aviation South‑China Smart Airport Construction Shenzhen Conference, Shenzhen Airport partnered with Tencent Cloud to publicly showcase the “Shenzhen Airport” mini‑program.

The mini‑program is the first domestic airport app that precisely recommends services based on passenger travel itineraries, covering outbound, inbound, transfer, and pick‑up scenarios, and offering 31 sub‑services such as indoor navigation, transportation, intelligent customer service, luggage tracking, etc.

Key technical solution: the OneID full‑process passenger travel service system. OneID provides a single digital identity that spans all four travel scenarios, unifying entry through mini‑program, app, and public account, and linking backend systems to enable behavior tracking, big‑data and AI‑driven personalized services.

Data security: the system implements encryption, authorization, authentication, auditing, and desensitization throughout the data lifecycle and complies with GDPR and other standards.

Overall Architecture (image omitted).

Rapid Development and Deployment : UI assets are stored in Cloud Development storage, paths in the cloud database, and the mini‑program fetches data via cloud functions with local caching, reducing release cycles dramatically.

Logging System : Instead of building a custom Elasticsearch logging pipeline, the project uses the built‑in cloud‑function logger. Example code:

const objCloud = require('wx-server-sdk');
objCloud.init({env: ENV});
const objLog = objCloud.logger();
objLog.info({});
objLog.error({});

Logs are searchable in the mini‑program management console, supporting structured queries for backend API calls and cloud‑function invocations.

Cache Strategy : Two‑level cache – client‑side UI configuration cache and server‑side key‑value cache in memory. Cache invalidation is handled manually via the admin console or automatically when cloud functions are updated. The document lists handling of cache expiration, hit, avalanche, penetration, and “stabbing” (high‑concurrency) scenarios.

Environment Management : Three environments (development, pre‑release, production) are defined. The mini‑program determines the active environment via __wxConfig.envVersion and connects to the corresponding cloud resources, preventing accidental deployment of test settings to production.

Admin Console : Provides CRUD operations for operational data, leveraging the mini‑program Cloud SDK to query and modify cloud database records and publish resources.

Conclusion : By leveraging Tencent Cloud Serverless and Cloud Development, the project eliminated the need for traditional server deployment, accelerated development (e.g., login and phone number retrieval reduced from 1 day to 5 minutes), saved at least five person‑days on logging, and currently runs 25 cloud functions with plans to expand.

Readers interested in Cloud Development can follow the “Tencent Cloud Cloud Development” public account.

cachingloggingmini programTencent CloudCloud DevelopmentOneID
Tencent Cloud Developer
Written by

Tencent Cloud Developer

Official Tencent Cloud community account that brings together developers, shares practical tech insights, and fosters an influential tech exchange community.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.