Oliveyoung Payment Story Part - 3

Oliveyoung's order completion process includes a lot of logic such as inventory verification, payment, and shipping information processing, and for data accuracy, all processes have been handled bundled into a single Transaction.

However, when traffic surged and multiple users attempted to modify data simultaneously, DB Lock occurred, which led to a Dead Lock where the data processing order got tangled, causing excessive use of system resources and risking service outages.

To resolve this, transaction separation was carried out, splitting the existing large transaction unit into individual transactions. There was a design process that considered complex product attributes such as 1+1 products, free gifts, and promotional products, but as a result, the structure was improved so that each item could be Committed independently.

As a result of load testing using Jmeter, it was confirmed that the numerous errors and Dead Locks that occurred before the improvement did not occur at all after the improvement. In the actual production environment as well, this proved a performance improvement whereby order processing operated stably even during events with high traffic.