Tagged articles
seckill
51 articles · Page 1 of 1

DabaoshiAug 20, 2026 · Backend Development
The article explains how to replace blocking Future with CompletableFuture for efficient asynchronous orchestration, covering task chaining, parallel execution, exception handling, and Fork/Join, and demonstrates a complete seckill order pipeline that reduces latency by parallelizing independent steps.
CompletableFutureConcurrencyForkJoin
0 likes · 19 min read

The article walks through the evolution of a flash‑sale inventory‑deduction system, starting with simple database row‑locking SQL, exposing its scalability limits, and progressively adding transaction trimming, Redis pre‑deduction, Lua atomic scripts, async pipelines, idempotency, reconciliation and robust engineering practices to handle extreme concurrency.
AsyncProcessingHighConcurrencyIdempotency
0 likes · 40 min read

This article provides a production‑grade, step‑by‑step engineering guide for designing a high‑concurrency seckill (flash‑sale) system that can sustain 100,000 QPS using Spring Boot, Redis with Lua scripts, asynchronous messaging, and comprehensive fault‑tolerance, monitoring, and scalability techniques.
LuaRedisSpring Boot
0 likes · 40 min read

This article presents a comprehensive, step‑by‑step analysis of building a flash‑sale (seckill) system that can survive instant traffic spikes, detailing seven essential design ideas such as static page delivery, token gating, Redis atomic decrement, asynchronous queuing, multi‑layer rate limiting, service isolation, idempotent processing, and end‑to‑end monitoring and recovery.
IdempotencyLuaMQ
0 likes · 28 min read

The article explains a MySQL kernel‑level merged seckill optimization that replaces traditional queue‑based flash‑sale handling, achieving up to 5‑fold throughput gains (up to 1.5 W/s) without requiring SQL changes, detailing background, performance results, bottleneck analysis, design of cache visibility, leader‑follower coordination, row‑lock refinements, binlog parallelism, and crash‑recovery considerations.
MySQLdatabase-optimizationhigh-concurrency
0 likes · 12 min read

The article details a MySQL kernel‑level merged‑seckill optimization that replaces traditional queue‑based flash‑sale handling, achieving up to 5.5× higher TPS (up to 23,543 TPS on 128 threads) and sustaining 1.5W+ orders per second, while remaining transparent to applications and preserving compatibility with existing SQL.
CacheLockMySQL
0 likes · 11 min read

This article walks through the design and implementation of a complete seckill (flash‑sale) system built on SpringBoot, MyBatis, MySQL, RabbitMQ and Redis, covering double MD5 password hashing, distributed sessions, unified exception handling, caching strategies, memory flags, pre‑decrement inventory, asynchronous order processing, oversell prevention, and rate limiting, with code snippets and UI screenshots.
Optimistic LockRabbitMQRedis
0 likes · 9 min read

During high‑traffic flash‑sale events like Double 11, malicious users can flood seckill APIs, causing service collapse and inventory errors; this article explains the business pain points and presents a multi‑layer anti‑scraping solution—including rate limiting, behavior detection, captchas, request signing, token mechanisms, and asynchronous order processing—with concrete Java implementations.
API SecurityCAPTCHAJava
0 likes · 7 min read

Learn how to design a robust, high‑performance seckill architecture that can endure millions of concurrent requests by breaking down business flow, defining precise technical metrics, and implementing a four‑layer system—access, traffic‑shaping, business logic, and data—using CDN, APISIX, Redis, RocketMQ, and MySQL with detailed code examples.
RocketMQTCCapixis
0 likes · 22 min read

This article demonstrates how to simulate a high‑concurrency flash‑sale scenario with SpringBoot and MySQL, analyzes why naive lock‑and‑transaction code causes overselling, and presents six refined solutions—including early locking, AOP, pessimistic and optimistic database locks, blocking queues, and Disruptor queues—along with performance observations and a concise summary.
ConcurrencyLockQueue
0 likes · 22 min read

This article examines common industry practices for handling massive e‑commerce flash‑sale traffic, detailing pressure‑distribution, Redis + MySQL, Redis + MQ, and Alibaba's Inventory Hint approaches, and explains how Lua scripts, transactional MQ messages, and database hints together ensure atomic stock deduction and consistency under extreme load.
Inventory HintMQRedis
0 likes · 13 min read

This article explores common overselling problems in high‑concurrency flash‑sale scenarios and presents seven practical solutions—including lock timing adjustments, AOP locking, pessimistic and optimistic database locks, and queue‑based approaches—each illustrated with SpringBoot code and performance test results.
ConcurrencyJavaLock
0 likes · 20 min read

This article analyzes a high‑concurrency flash‑sale scenario using SpringBoot, MySQL, and JMeter, demonstrates seven implementations—from service‑level locks to AOP, pessimistic/optimistic locks, and queue‑based designs—examines their trade‑offs with concrete code, test results, and practical recommendations.
ConcurrencyJMeterLock
0 likes · 20 min read

This article demonstrates how to simulate a high‑concurrency flash‑sale scenario using SpringBoot, MySQL, Mybatis‑Plus and JMeter, analyzes the overselling problem caused by premature lock release, and presents seven solutions—including lock‑first strategies, AOP, pessimistic and optimistic locks, and queue‑based approaches—along with code samples and test results.
AOPConcurrencyJMeter
0 likes · 19 min read

This article details the design and implementation of a Java SpringBoot seckill system, covering its architecture, technology stack, double‑MD5 password encryption, distributed session management with Redis, unified exception handling, page and object caching, static page generation, memory‑flag plus Redis pre‑decrement and RabbitMQ asynchronous order processing, oversell prevention, and API rate limiting, accompanied by key code snippets.
JavaRabbitMQRedis
0 likes · 11 min read

This article presents a step‑by‑step technical walkthrough of a SpringBoot‑based Seckill project, covering password MD5 hashing, distributed session management, unified exception handling, page and object caching, static page generation, memory flag with Redis pre‑decrement and RabbitMQ async processing, oversell prevention, and API rate limiting, followed by a visual demonstration of the system’s UI and source code download.
RabbitMQRedisSpringBoot
0 likes · 9 min read

This article presents a concise tutorial on building a flash‑sale (Seckill) system with SpringBoot, MySQL, Redis, RabbitMQ and a basic HTML/JQuery front‑end, covering architecture, key features, code snippets, over‑selling prevention, rate limiting, and deployment screenshots.
BackendJavaMySQL
0 likes · 8 min read

This article analyzes the overselling problem that occurs during high‑concurrency flash‑sale (seckill) operations and presents seven concrete solutions—including improved lock placement, AOP‑based locking, three types of database locks, optimistic locking, a blocking‑queue approach, and a Disruptor queue—complete with SpringBoot 2.5.7 code samples, performance test results, and practical recommendations.
ConcurrencyDistributedSystemsSpringBoot
0 likes · 20 min read

This article details the design and implementation of a Java‑based flash‑sale (Seckill) system using SpringBoot, Redis, RabbitMQ, and related technologies, covering architecture, security, caching, asynchronous processing, oversell prevention, and rate‑limiting techniques.
JavaRabbitMQRedis
0 likes · 7 min read

This article introduces a simplified Seckill (flash‑sale) system built with SpringBoot, detailing its overall architecture, key backend techniques such as distributed sessions, Redis caching, RabbitMQ asynchronous ordering, security measures, oversell prevention, rate limiting, and provides essential code snippets and deployment screenshots.
BackendJavaRabbitMQ
0 likes · 8 min read

This article details the design and implementation of a Java-based Seckill (flash‑sale) platform built with SpringBoot, MySQL, Redis, RabbitMQ, and front‑end technologies, covering password hashing, distributed sessions, caching strategies, asynchronous order processing, oversell prevention, rate limiting, and provides code snippets and deployment screenshots.
JavaRabbitMQRedis
0 likes · 8 min read

This article demonstrates how to simulate a high‑concurrency flash‑sale scenario using SpringBoot, MySQL and JMeter, analyzes why naive lock‑and‑transaction code causes overselling, and presents six refined solutions—including controller‑level locking, AOP locking, pessimistic and optimistic database locks, and queue‑based approaches—along with performance test results.
AOPJMeterLock
0 likes · 20 min read

This article demonstrates how to simulate high‑concurrency flash‑sale scenarios using SpringBoot, MySQL, and JMeter, and compares seven approaches—including lock‑based, AOP, pessimistic and optimistic locking, and queue‑based solutions such as BlockingQueue and Disruptor—to prevent overselling and improve performance.
ConcurrencyQueueSpringBoot
0 likes · 19 min read

This article explains how to build a high‑concurrency ticket‑seckill service that can handle millions of requests by combining distributed load‑balancing (OSPF, LVS, Nginx weighted round‑robin), a pre‑deduction stock strategy using local memory and Redis with Lua scripts, and a Go‑based HTTP server, and it demonstrates performance testing results.
GoRedishigh concurrency
0 likes · 19 min read

This article presents a comprehensive analysis of flash‑sale (seckill) business characteristics, technical challenges, and architectural principles, offering detailed backend design solutions—including request interception, queue management, database sharding, caching strategies, optimistic locking, and anti‑cheating measures—to achieve high‑throughput, low‑latency processing for millions of concurrent users.
BackendQueuedatabase
0 likes · 36 min read

The article explains the characteristics of flash‑sale scenarios, presents core design principles such as rate limiting, peak shaving, asynchronous processing and scalability, and details a complete backend and frontend architecture—including Redis‑based queueing and caching—to build a robust, high‑throughput seckill system.
Asynchronous ProcessingRedisdistributed systems
0 likes · 12 min read

This article analyzes the extreme‑traffic problem of Chinese train ticket sales, presents a multi‑layer load‑balancing architecture with Nginx weighted round‑robin, demonstrates Go and Redis code for local and global stock deduction, and shows benchmark results proving that a single machine can handle over 4 000 requests per second while preventing oversell and few‑sell.
GoRedisbackend development
0 likes · 20 min read

The article analyzes flash‑sale business flow, outlines the technical challenges of massive concurrent requests, and presents a comprehensive backend architecture—including request isolation, queueing, caching, sharding, replication, optimistic locking, and overload protection—to ensure correctness, scalability, and availability of seckill services.
Optimistic Lockbackend architecturehigh concurrency
0 likes · 34 min read

This article explains how a naïve SpringBoot SecKill implementation can cause overselling, then introduces Redis commands (SETNX, EXPIRE, GETSET) and a custom RedisLock component to achieve safe distributed locking, avoid deadlocks, and ensure accurate inventory updates during high‑concurrency flash‑sale events.
Distributed LockJavaRedis
0 likes · 10 min read

This article examines a real‑world flash‑sale incident where Redis distributed locks failed, causing severe overselling, and presents root‑cause analysis, safer lock implementation with Lua scripts, atomic stock handling, refactored Java code, and deeper reflections on lock necessity and further optimizations.
ConcurrencyDistributed LockJava
0 likes · 10 min read

This guide walks you through installing the jd_seckill Python script, configuring JD.com credentials, setting the purchase time, and executing the tool to automate Moutai flash sales, including environment setup, required dependencies, and step‑by‑step usage instructions.
JD.comMoutaiPython
0 likes · 6 min read

This article analyzes a real‑world flash‑sale incident where a Redis distributed lock expired under high load, causing a 100‑bottle product to be oversold, and presents safer lock implementations, atomic stock checks, and performance‑oriented redesigns to prevent such failures.
BackendDistributed LockJava
0 likes · 11 min read

This article uses a sci‑fi story set on the A‑731 e‑commerce planet to illustrate the core principles of flash‑sale systems, including single‑responsibility services, independent deployment, stock pre‑heating, request encryption, static‑dynamic separation, traffic shaping, rate limiting, queue‑based load smoothing, and the role of Redis, Nginx, CDN and Redisson in handling massive order spikes.
flash salerate limitingseckill
0 likes · 10 min read

This article details the business flow analysis, functional decomposition, database schema, API design, and high‑concurrency implementation of a WeChat red‑packet and seckill system, showcasing Redis atomic decrement, Bloom filter usage, Lua scripts, JMeter load testing, and integration with SpringBoot.
Bloom FilterJavaRedis
0 likes · 11 min read

This article examines a real-world over‑sell incident caused by an unsafe Redis distributed lock in a high‑traffic seckill service, analyzes the root causes such as lock expiration and non‑atomic stock checks, and presents safer lock implementations, atomic stock operations, and refactored code to prevent future overselling.
Distributed LockJavaatomicity
0 likes · 11 min read

This article explains the core concepts, architecture, and practical techniques—including load‑balancing, caching, async processing, and Redis sharding—required to design and implement a high‑concurrency seckill system that can handle millions of requests in a short time window.
async processingbackend architecturehigh concurrency
0 likes · 19 min read


ITPUBMay 27, 2020 · Backend Development
This article compares five flash‑sale (seckill) system designs, detailing their implementation principles, pros and cons, fairness, scalability, and provides guidance on selecting the most suitable architecture for different traffic and operational constraints.
fairnessflash salescalability
0 likes · 7 min read

This article examines the architectural design of flash‑sale (seckill) systems, covering high performance through dynamic‑static separation, hotspot optimization, consistency handling for inventory deduction, and high‑availability techniques such as traffic shaping, queuing, and fallback plans.
ConsistencyHigh Availabilityarchitecture
0 likes · 30 min read

This article explains how to build a high‑concurrency train‑ticket flash‑sale system that can handle millions of requests by combining layered load‑balancing, Nginx weighted round‑robin, in‑memory stock deduction, Redis atomic Lua scripts, and a Go HTTP service with channel‑based concurrency control, and it provides performance test results and source code.
GoRedishigh concurrency
0 likes · 18 min read

This article analyzes the architecture, load‑balancing strategies, stock‑deduction techniques, and Go/Redis implementation needed to support a million concurrent users purchasing ten thousand train tickets without overselling or underselling.
BackendGoRedis
0 likes · 20 min read

This article presents a comprehensive design for a flash‑sale (seckill) system that handles massive simultaneous requests by combining load balancing, distributed locking, message queues, cache strategies, and fault‑tolerant deployment, and includes a complete Spring Boot code example with detailed architectural diagrams.
backend architecturehigh concurrencyseckill
0 likes · 7 min read

This article explains the business background of a flash‑sale (seckill) scenario, analyzes naive locking approaches, introduces Redis‑based distributed locks, and provides a complete Java demo with custom annotations, dynamic proxies, and a multithreaded test to ensure correct inventory decrement under high concurrency.
Distributed LockJavaRedis
0 likes · 15 min read

This article explains the purpose of the Service layer in a Java SSM‑based high‑concurrency seckill project, walks through interface design, DTO/VO/PO concepts, provides full Service implementation with transaction management, custom exceptions, enumeration for status codes, Spring XML configuration, and unit testing examples.
JavaService LayerSpring
0 likes · 15 min read

This guide walks through downloading and installing Redis, adding Java dependencies, creating a Redis DAO with Protostuff serialization, configuring Spring beans, caching seckill data, implementing a MySQL stored procedure for atomic execution, mapping it with MyBatis, updating service and controller layers, and testing the entire workflow.
JavaMySQLRedis
0 likes · 8 min read

This article presents a comprehensive design of a flash‑sale (seckill) architecture, covering business characteristics, user scale, layered system components, optimization strategies, full‑link stress testing, and a complete SpringBoot code example with distributed locks, message queues, and database sharding.
Distributed Lockbackend architecturehigh concurrency
0 likes · 7 min read

This article explains why rate limiting is essential for flash‑sale (seckill) systems, compares token‑bucket and leaky‑bucket algorithms, and provides concrete Tomcat, Nginx, OpenResty, and Guava configurations along with code snippets and load‑testing results to help engineers implement robust throttling.
Leaky BucketOpenRestyTomcat
0 likes · 14 min read

This article explains why rate limiting is essential for flash‑sale (seckill) services, compares token‑bucket and leaky‑bucket algorithms, and provides practical configuration examples for Tomcat, Nginx, and OpenResty, along with testing methods and code snippets.
OpenRestyTomcatload-testing
0 likes · 14 min read

This article explains why rate limiting is essential for large‑scale flash‑sale (seckill) services, introduces token‑bucket and leaky‑bucket algorithms, and demonstrates practical implementations using Tomcat thread pools, Nginx, OpenResty, and Guava RateLimiter together with stress‑testing commands.
Tomcatnginxrate limiting
0 likes · 12 min read

This article walks through the step‑by‑step implementation of a high‑throughput flash‑sale (seckill) service in Java, covering request flow, database schema, optimistic‑locking updates, Redis‑based rate limiting, CI scripts, and optional Kafka asynchronous order processing to achieve fast, reliable, and scalable sales handling.
JavaOptimisticLockingRateLimiting
0 likes · 18 min read

This article dissects the technical challenges of building a high‑concurrency flash‑sale (seckill) system—covering business analysis, traffic isolation, static page caching, CDN bandwidth, dynamic order URLs, request throttling, database sharding, optimistic locking, and anti‑cheat mechanisms—while presenting concrete architectural principles and code examples.
Optimistic Lockdistributed systemshigh concurrency
0 likes · 36 min read


21CTOAug 10, 2017 · Backend Development
This article explains how to design and implement a Java‑based flash‑sale (seckill) system that can handle tens of thousands of concurrent requests, covering entity modeling, DAO methods, service logic, controller handling, a concurrency simulation test, and an improved locking strategy to prevent overselling.
ConcurrencyJPAJava
0 likes · 9 min read
