BattleShip Technology · Inside the Backend

BigPengCloud Microservice Architecture

This is the engine behind Qingniu Dunan. From the Alipay mini-app to the gateway, microservices, and infrastructure, one five-layer diagram explains how data flows and how security holds.

Crypto Frontier

Asymmetric Encryption, Ready for the Quantum Era

Asymmetric encryption and key security sit at the core of the platform. Our Java 26 runtime already ships post-quantum algorithms as first-class APIs, while post-quantum hybrid TLS key exchange is delivered at the traffic-termination layer (Nginx on OpenSSL 3.5+)—defending today against "harvest now, decrypt later."

Post-Quantum Algorithms, Built In

The Java platform now includes NIST post-quantum standards as first-class APIs: ML-KEM (FIPS 203) for key encapsulation and ML-DSA (FIPS 204) for digital signatures, alongside classic algorithms.

Hybrid Key Exchange in TLS

Our TLS termination layer (OpenSSL 3.5+) enables the post-quantum hybrid key exchange X25519MLKEM768 for TLS 1.3: classic ECDH layered with ML-KEM—the channel stays secure as long as either algorithm holds, with no runtime upgrade required.

Against Harvest-Now-Decrypt-Later

Ciphertext captured today could be decrypted by future quantum computers. Hybrid key exchange gives long-lived, sensitive visitor data forward protection from the transport layer up.

A Smooth Overlay on What We Run

Post-quantum capability layers on top of our dual SM-cipher and RSA/AES envelope encryption with no change to the X.509 certificate chain—an incremental, zero-downtime upgrade path.

Runtime baseline is Java 26; post-quantum hybrid key exchange is enabled at the TLS termination layer (OpenSSL 3.5+) independently of any JDK upgrade, rolling out entry by entry with our canary releases.

Architecture Map

The Five-Layer Diagram

Read top to bottom: requests enter through the edge layer, are dispatched to business microservices, share one governance foundation, and land on clustered infrastructure.

Client Layer

Clients

Every entry point for users and external systems, all over HTTPS with request signatures.

Alipay Mini-app

Visitor & interview registration

PC Admin Console

Park & enterprise management

Cli

Ops inspection · AK/SK signing

Third-party Platforms

Alipay open capabilities, etc.

Edge Layer

Edge & Gateway

The single front door: dynamic routing, unified JWT auth, rate limiting, and canary releases happen here.

Nginx

SSL termination · reverse proxy

API Gateway

Spring Cloud Gateway · WebFlux

Business Services

Independently deployable microservices split by domain, each owning its data source, routed by path prefix.

Auth Center

Multi-strategy login · JWT issuing

System Mgmt

Users · roles · menus · logs

Visit Center

Parks · companies · decryption audit

Mini-app Service

Encrypted booking · certificates

CRM

Sales management

Resource Service

Files · SMS · email · inbox

Workflow Engine

Warm-Flow approvals

Governance & Shared

Cross-cutting capabilities distilled into 33 shared modules and API contracts, plugged in by services on demand.

Dubbo RPC

Service-to-service calls · registry discovery

API Contracts

Shared remote interface definitions

Security & Crypto

JWT checks · envelope encryption · SM ciphers · idempotency

Data Access

Multi-datasource · data scope · sensitive masking

Messaging & Push

WebSocket · SSE · Spring Cloud Bus

Cloud Integrations

Object storage · SMS · email · social login

Observability

Operation logs · SkyWalking tracing · Prometheus metrics

Dynamic Routing

Nacos route table · canary release

Infrastructure

All stateful capabilities run as clustered middleware, so business services stay stateless and scale horizontally.

Nacos Cluster

Registry · config center

Redis Sentinel

Cache · distributed locks

Vitess

MySQL cluster proxy · per-service schemas

Seata

Distributed transactions

SnailJob

Distributed job scheduling

Vault

Centralized secrets management

Observability

Boot Admin · Prometheus · SkyWalking

Cloud Services

Object storage · SMS · email

How It Connects

How Data Flows

Four key links behind the arrows of this diagram.

HTTPS

Clients → gateway: every request carries Timestamp + Nonce + HMAC signature, replay-proof end to end.

Dubbo RPC

Service → service: a binary high-speed protocol resolved through the registry, with interfaces defined in shared API contracts.

Nacos

All services: registration, discovery, and live config updates; even the gateway route table is published through Nacos.

Vault

Zero plaintext config: production credentials and keys are injected via placeholders at startup, never committed to the repo.

Deployment & Release

Multi-Entry Deployment, Zero-Downtime Updates

The system is multi-entry by design: four server entries serve in parallel today and more can join anytime; releases combine canary rollout with graceful updates.

Server entries · today

N+

Elastic entry scaling

Downtime · graceful update

Parallel Entries

Four server entries serve traffic simultaneously under unified distribution; a new entry takes requests as soon as it registers — scaling never reshapes the architecture.

Canary Release

A new build lands on a single entry with a sliver of traffic first; the gateway route table switches dynamically, rolling out fully only once stable, with fast rollback on anomalies.

Graceful Update

Before updating, an instance deregisters from the registry and drains in-flight requests, then swaps its package and restarts smoothly — invisible to users.

Incremental Dependency Sync

Shared dependencies are packaged per service and synced to each entry incrementally, sharply shortening the update window.

Design Traits

Architecture Choices Made for Security and Change

Architecture is not a noun soup — it is what lets every change land small and steady.

Zero-knowledge Encryption

Dual-algorithm envelope encryption (SM national crypto and RSA+AES) runs deep inside the services; keys belong to the park, the platform stores ciphertext only.

One Security Boundary

The gateway validates JWT centrally, while the auth center issues tokens for password / SMS / QR / mini-app / AK-SK login strategies.

High Availability

Three-node registry, Redis Sentinel, stateless services — automatic failover and horizontal scaling.

Progressive Release

Gateway canary routing runs two versions side by side; new builds get a sliver of traffic first and roll back in seconds.

Tech Stack

Key Components and Versions

Built entirely on mainstream open source, with versions at the leading edge.

Java 26

Virtual threads · post-quantum crypto

Spring Boot 4

Application framework

Spring Cloud 2025

Gateway · governance

Apache Dubbo 3

Service RPC

Nacos 3

Registry & config

MyBatis-Plus

Multi-datasource ORM

Redisson

Cache & locks

Seata

Distributed transactions

Transparent architecture, provable security

Everything Qingniu Dunan does is built on this backend. Try it in the Alipay mini-app, or talk to us about the technical details.