From NodeJS Backend to Large-Scale React Native: Our ‘Big Wireless’ Team Reorg Explained

Introduction

The team reorganized into a "big wireless" structure that separates an architecture group from a business group to align technical capabilities with overall business value.

NodeJS Role Evolution

NodeJS was originally used for pure server‑side development with the goal of matching Java’s engineering capabilities. After evaluating the cost of service‑side rendering and front‑back separation, the team decided to phase out pure NodeJS backend work and consolidate server responsibilities onto the Java stack. NodeJS developers are now focused on areas where asynchronous performance and rapid development are advantageous, such as a gateway system that handles API entry, routing, and service tiering.

Current "Big Wireless" Architecture

The gateway system combines multiple technologies:

Nginx for the network layer and request routing.

Lua for lightweight heartbeat checks.

NodeJS for rule management and dynamic configuration.

This multi‑stack approach serves both front‑end and back‑end requirements while leveraging each technology’s strengths.

Large‑Scale React Native Adoption

Two primary problems drove the adoption of React Native:

Native development required roughly twice the effort per developer compared to a cross‑platform solution.

Maintaining a unified client roadmap across separate native codebases was increasingly difficult.

Key technical actions taken:

Designed a custom scaffolding toolchain covering project creation, debugging, release, and version‑update processes.

Implemented a strict bundle‑dependency mechanism: RN bundles are packaged at build time; hot‑updates are limited to bug‑fixes only, preventing runtime feature changes.

Built a client SDK that provides:

Bundle dependency management.

Native component wrappers.

RN‑Native‑H5 communication protocols.

Performance and crash monitoring.

Created a comprehensive development framework that includes a design‑system‑driven component library, native component wrappers, tooling, documentation, and example projects. This enables rapid delivery of RN projects with minimal exposure to underlying RN concepts.

The resulting RN ecosystem abstracts most React concepts, enforces strong version dependencies, and tightly integrates with native and H5 layers.

Architecture Group Functions

The dedicated architecture group centralizes technical direction and shared infrastructure. Its responsibilities are organized into three sub‑teams:

Cross‑Platform Experience Team : delivers RN solutions, performance optimizations, and process standards.

Client/Front‑End Architecture Team : defines engineering standards, provides mock systems, static resource services, and shared tooling.

NodeJS Middleware Team : offers gateway services, server‑side rendering, RN module management, static hosting, and messaging services.

Architecture Workflow

The group follows a repeatable workflow to ensure analysis and communication dominate over coding:

Problem identification → Research → Initial proposal → Discussion → Full solution → Architecture diagram → Business review → Planning → Implementation → Rollout

This process keeps code contribution to roughly 20 % of the team’s effort.

Core Takeaways

Evaluate technologies against concrete business scenarios rather than following trends.

Focus on the core value a technology delivers; avoid using a stack solely for its novelty.

All technical domains, including front‑end and middleware, require deep expertise to create sustainable value.