Serverless Migration of the Rights Play Platform with Ring Architecture
The Rights Play Platform migrated from the in‑house Ring JVM container framework to a Serverless architecture, eliminating custom permission logic and memory‑leak risks while achieving roughly 30% faster development cycles, 80% shorter deployments, automatic scaling, unified base services, and significantly lower operational costs.
Background: The Taobao Rights Platform supports diverse marketing IP and lightweight interactive demands, requiring rapid delivery and high development efficiency.
The Rights Play Platform was created to provide a reusable marketing capability system, reducing development cost and improving delivery speed.
Initial solution: Ring containerization. Ring is an in‑house JVM container framework offering hot deployment and on‑demand machine grouping. It consists of a host application providing shared services and multiple business containers (farjar) that can be mounted independently, enabling second‑level deployment and isolation.
Advantages of Ring: high efficiency through hot‑deployment, strong isolation via machine grouping, and clear separation of platform and business development responsibilities.
Limitations: Ring is designed for extensible business modules, which does not perfectly fit the Rights Play Platform’s independent services; it introduces permission and role constraints and adds custom logic that raises maintenance and memory‑leak risks.
Transition to Serverless: After evaluating Ring, the team embraced Serverless to further simplify the R&D workflow. Serverless separates application logic from infrastructure, providing automatic scaling, zero‑ops, rapid deployment, and unified base services.
Key Serverless features highlighted: no‑ops (infrastructure managed by the platform), lower cost through elastic scaling, fast delivery via function‑level deployment, and unified architecture where base services (JDK, middleware) are centrally maintained.
Serverless also introduces a plug‑in mechanism for shared business capabilities, offering class isolation, controlled class export, lifecycle management, and unified upgrade paths.
Benefits observed during the Double‑11 peak: development cycle reduced by ~30%, deployment time cut by ~80%, and overall R&D efficiency and operational cost significantly improved.
The team plans to continue expanding Serverless adoption across other services, expecting further innovation and productivity gains.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.