Modular Development and SOP Practices for High‑Velocity Revenue Activities

This article analyzes the challenges faced by developers of revenue‑driven activities in fast‑paced internet services, distinguishing between core functional business (e.g., gifting, PK) and growth‑oriented activities (e.g., promotional events). The rapid iteration, massive logic volume, and strict stability requirements create a gap between decision‑making and implementation, leading to frequent bugs, missed deadlines, and high operational costs.

Three fundamental problems are identified:

Human‑centric bottleneck: Scaling the business relies heavily on manual effort, making bugs inevitable as code volume grows.

Insufficient standardization and digitization: Existing reusable systems cannot keep up with the ever‑changing activity patterns, limiting effective reuse.

R&D model lagging behind business cycles: The development process does not anticipate the accelerated pace of growth‑type activities, causing reactive rather than proactive solutions.

To address these issues, the authors propose a "building‑block" (积木式) development approach, consisting of four pillars:

Abstract immutable capabilities and layer them to maximize reuse.

Define SOP (Standard Operating Procedure) workflows to hide detailed implementation.

Automate repetitive tasks through tooling.

Modularize SDKs for the final integration step.

The architecture is divided into three layers:

Base layer: Core data structures (uid, score_id, extend, num, expire) that support generic operations such as issuance, deduction, and balance queries.

Block layer: Pre‑packaged business patterns (e.g., automatic ranking, task enrollment) that can be enabled via configuration.

Customization layer: Hooks and custom logic for edge cases that cannot be covered by the previous layers.

Standardized SOP processes ensure that configuration creation, online‑to‑test synchronization, and pre‑release rehearsals are repeatable and low‑risk. Automation tools include reward‑validation scripts and a Golang text/template based code‑generation utility that scaffolds new handlers, reducing manual copy‑paste errors.

Empirical results show that from H2 2021 to H2 2022 the number of delivered activities doubled (21 → 41) while team size remained constant, average bugs per activity dropped by 33 %, and overall operational pressure decreased. The modular approach thus improves delivery speed, quality, and maintainability for large‑scale, fast‑moving revenue activities.