Operations 16 min read

JD Digital Technology's 6.18 Promotion Technical Preparation Overview

The article details JD Digital Technology's comprehensive technical preparation for the 6.18 shopping festival, describing how 13 cross‑functional teams performed system scaling, multi‑layer performance testing, architecture upgrades, risk management, data pipeline enhancements, and 24/7 monitoring to ensure a stable, high‑throughput promotion environment.

JD Retail Technology
JD Retail Technology
JD Retail Technology
JD Digital Technology's 6.18 Promotion Technical Preparation Overview

On April 16, 2020, JD Digital Technology entered the 6.18 promotion preparation phase, mobilizing 13 teams—including Payment, Open Platform, Consumer Finance, Wealth Management, Insurance, Enterprise Finance, User Product, Ecosystem Operations, Digital Marketing, Risk Management, Customer Service, Data Assets, and Operations—to conduct extensive system checks, capacity expansions, and rehearsals under the direction of Open Platform lead Shi Lirong.

The Payment team focused on optimizing payment read/write pipelines, upgrading components, tuning databases, and establishing real‑time monitoring and downgrade plans to guarantee rapid settlement and rapid response to incidents.

The Open Platform team refined core services, performed two capacity expansions, multiple read/write stress tests, and four end‑to‑end mall rehearsals, while also preparing monitoring dashboards for the financial app and handling new traffic channels such as Beijing consumption coupons.

Consumer Finance highlighted a systematic preparation process—system inventory, read/write stress tests, pre‑plan drills—and even provided meals for teammates working late nights.

Wealth Management emphasized database and cache optimizations, multiple rounds of pressure testing, and a staged rollout of a “small treasury” system to sustain high query loads.

Insurance detailed a multi‑step scaling strategy—capacity expansion, interface refinement, stress testing, permission audits, and data archiving—while sharing personal anecdotes of team members working through the night.

Enterprise Finance improved large‑table storage performance, resolved multi‑billion‑record latency issues, and highlighted the dedication of team members working under intense pressure.

User Product described its focus on user experience, high delivery rates, low incident rates, and a 7×24 on‑call rotation to ensure service stability during peak traffic.

Ecosystem Operations performed comprehensive component upgrades, JDK updates, and traffic assessments, adding new channels like Jingxi and implementing dynamic traffic control and performance profiling tools.

Digital Marketing optimized core systems for concurrency, added monitoring, and completed capacity expansions to meet the 6.18 challenge.

Risk Management expanded testing for payment coupons, marketing discounts, and rapid payment scenarios, introduced custom whitelist caching, automated strategy downgrade, and supported the rapid‑payment project with MQ sharding and streaming calculations.

Customer Service enhanced IVR interactions, delivered 14 new features, integrated AI‑driven training, and built a navigation system to improve agent efficiency and reduce turnover.

Data Assets upgraded offline and real‑time data pipelines, introduced intelligent scheduling, multi‑region deployment, and new analytics tools such as a real‑time data dashboard and 6.18 data war report.

Operations coordinated over 300 stress tests, performed security scans, upgraded MySQL instances, optimized resource allocation, and maintained 24/7 monitoring to ensure system stability throughout the promotion.

backendoperationsPerformance TestingJD6.18Technical Preparation
JD Retail Technology
Written by

JD Retail Technology

Official platform of JD Retail Technology, delivering insightful R&D news and a deep look into the lives and work of technologists.

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.