How to prevent duplicate submission in Spring Boot

In this issue, the editor will bring you about how to prevent repeated submission in Spring Boot. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

Train of thought

1. Custom annotation @ NoRepeatSubmit marks the submission request in all Controller

2. Intercept all methods marked @ NoRepeatSubmit through AOP

3. Before the execution of the business method, obtain the current user's token (or JSessionId) + current request address as a unique KEY to acquire the Redis distributed lock (if acquired concurrently at this time, only one thread will successfully acquire the lock)

4. Release the lock after the execution of the business method

Only AOP classes and test classes are posted here

Multithreaded testing

The test code is as follows, simulating ten requests to be submitted at the same time

Duplicate submission was successfully prevented. The console log is as follows. You can see that the startup time of ten threads was initiated almost at the same time, and only one request was submitted successfully.

This is how to prevent duplicate submissions in the Spring Boot shared by the editor. If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.