3 posts
This article shows how to use Spring AOP to separate distributed-lock handling completely from business logic. When you use the Lock interface for concurrency control, try-finally blocks and lock-management code can overwhelm the business logic. Just as Spring's @Transactional simplifies transaction management, we will solve this problem with a DistributedLock aspect and extend @DistributedLock with a SpEL evaluator modeled after Spring Cache.
This article continues from the previous post, "Understanding Pessimistic Locks Through a Like Feature." It corrects the misconception that "Lettuce supports only spin locks" and explains how Spring RedisLockRegistry's Pub/Sub lock mode can implement an efficient distributed lock without Redisson.
Suppose we are designing a first-come, first-served event system. The requirements are listed below. If 1,000 people request 100 available items at the same time, how can we ensure that exactly 100 people receive one? The solutions commonly proposed in this situation are listed below.