Spring boot interface idempotent plug-in use

Cool zz 2020-11-09 12:00:47
spring boot interface idempotent plug-in


An overview of idempotent

  • Idempotency was originally a mathematical concept , Even if the formula :f(x)=f(f(x)) The mathematical nature of being able to establish . In the field of programming , To the same system , Use the same conditions , One request and repeated multiple requests have the same impact on system resources .

  • Idempotent is a very important concept in distributed system design , Interfaces with this property are always designed with such a concept : When an exception occurs in the calling interface and repeated attempts are made , It will always cause losses that the system can't bear , So we have to stop this phenomenon .

  • There are many ways to achieve idempotency , At present, the mechanism based on request token is widely used . Its core idea is to generate a unique certificate for each operation , That is to say token. One token There is only one execution right at each stage of the operation , Once the execution is successful, the execution result is saved . For repeated requests , The same result ( Report errors ) etc. . Reference resources 《 On idempotency 》

Idempotent processing implements

Join the rely on

<dependency>
<groupId>com.pig4cloud.plugin</groupId>
<artifactId>idempotent-spring-boot-starter</artifactId>
<version>0.0.1</version>
</dependency>
spring:
redis:
host: 127.0.0.1
port: 6379

Interface

@Idempotent(key = "#key", expireTime = 10, info = " Please do not repeat the inquiry ")
@GetMapping("/test")
public String test(String key) {
return "success";
}

test

  • 10 Independent thread requests

  • Execute view results ,10 Only one request will succeed

  • Check background exception report error ,9 Exception error (s) met expectations

idempotent Note that

  • key: The unique identity of an idempotent operation , Use spring el expression use # To reference method parameters . If it can be blank, the current url + args Make the unique identification of the request

  • expireTime: The period of validity Default :1 The validity period should be longer than the program execution time , Otherwise, the request may come in

  • timeUnit: Time unit Default :s ( second )

  • info: Idempotent failure message , Customizable

  • delKey: Whether to delete after the business is completed key true: Delete false: Don't delete

Idempotent processing design principle

Process design reference

  • 1. Before the request begins , according to key Inquire about It turns out that : Report errors No results were found : Deposit in key-value-expireTime key=ip+url+args

  • 2. After request , Delete directly key No matter key Whether there is , Delete directly Whether or not to delete , Configurable

  • 3.expireTime Expiration time , Prevent a request from getting stuck , It will keep blocking , Beyond the expiration date , Automatically delete The expiration time is longer than the business execution time , It needs to be evaluated roughly ;

  • 4. This scheme is directly related to the interface request level .

  • 5. The expiration time needs to be greater than the business execution time , Otherwise, the business request 1 It's still in execution , The front end is not masked , Or users jump to the page and come back to make repeated requests 2, At the business level , The results are still not as expected .

  • 6. Suggest delKey = false. Even if the business is done , Don't delete key, Forced lock expireTime Time for . The prevention of 5 What happened .

  • 7. Realize the idea : The same request ip And interface , Requests with the same parameters , stay expireTime Many requests from within , Only one success is allowed .

  • 8. The page is masked , Database level unique index , Query first and then add , We should deal with it all .

  • 9. This annotation is only used for idempotent , Not for locks ,100 This kind of pressure test is carried out simultaneously , There will be problems , It doesn't make sense in this situation , In reality, users don't show up 1s perhaps 3s It was sent manually in 50 A or 100 Duplicate requests , Or under the weak network 100 Duplicate requests ;

summary

Project recommend : Spring Cloud 、Spring Security OAuth2 Of RBAC Authority management system Welcome to your attention

版权声明
本文为[Cool zz]所创,转载请带上原文链接,感谢

  1. 【计算机网络 12(1),尚学堂马士兵Java视频教程
  2. 【程序猿历程,史上最全的Java面试题集锦在这里
  3. 【程序猿历程(1),Javaweb视频教程百度云
  4. Notes on MySQL 45 lectures (1-7)
  5. [computer network 12 (1), Shang Xuetang Ma soldier java video tutorial
  6. The most complete collection of Java interview questions in history is here
  7. [process of program ape (1), JavaWeb video tutorial, baidu cloud
  8. Notes on MySQL 45 lectures (1-7)
  9. 精进 Spring Boot 03:Spring Boot 的配置文件和配置管理,以及用三种方式读取配置文件
  10. Refined spring boot 03: spring boot configuration files and configuration management, and reading configuration files in three ways
  11. 精进 Spring Boot 03:Spring Boot 的配置文件和配置管理,以及用三种方式读取配置文件
  12. Refined spring boot 03: spring boot configuration files and configuration management, and reading configuration files in three ways
  13. 【递归,Java传智播客笔记
  14. [recursion, Java intelligence podcast notes
  15. [adhere to painting for 386 days] the beginning of spring of 24 solar terms
  16. K8S系列第八篇(Service、EndPoints以及高可用kubeadm部署)
  17. K8s Series Part 8 (service, endpoints and high availability kubeadm deployment)
  18. 【重识 HTML (3),350道Java面试真题分享
  19. 【重识 HTML (2),Java并发编程必会的多线程你竟然还不会
  20. 【重识 HTML (1),二本Java小菜鸟4面字节跳动被秒成渣渣
  21. [re recognize HTML (3) and share 350 real Java interview questions
  22. [re recognize HTML (2). Multithreading is a must for Java Concurrent Programming. How dare you not
  23. [re recognize HTML (1), two Java rookies' 4-sided bytes beat and become slag in seconds
  24. 造轮子系列之RPC 1:如何从零开始开发RPC框架
  25. RPC 1: how to develop RPC framework from scratch
  26. 造轮子系列之RPC 1:如何从零开始开发RPC框架
  27. RPC 1: how to develop RPC framework from scratch
  28. 一次性捋清楚吧,对乱糟糟的,Spring事务扩展机制
  29. 一文彻底弄懂如何选择抽象类还是接口,连续四年百度Java岗必问面试题
  30. Redis常用命令
  31. 一双拖鞋引发的血案,狂神说Java系列笔记
  32. 一、mysql基础安装
  33. 一位程序员的独白:尽管我一生坎坷,Java框架面试基础
  34. Clear it all at once. For the messy, spring transaction extension mechanism
  35. A thorough understanding of how to choose abstract classes or interfaces, baidu Java post must ask interview questions for four consecutive years
  36. Redis common commands
  37. A pair of slippers triggered the murder, crazy God said java series notes
  38. 1、 MySQL basic installation
  39. Monologue of a programmer: despite my ups and downs in my life, Java framework is the foundation of interview
  40. 【大厂面试】三面三问Spring循环依赖,请一定要把这篇看完(建议收藏)
  41. 一线互联网企业中,springboot入门项目
  42. 一篇文带你入门SSM框架Spring开发,帮你快速拿Offer
  43. 【面试资料】Java全集、微服务、大数据、数据结构与算法、机器学习知识最全总结,283页pdf
  44. 【leetcode刷题】24.数组中重复的数字——Java版
  45. 【leetcode刷题】23.对称二叉树——Java版
  46. 【leetcode刷题】22.二叉树的中序遍历——Java版
  47. 【leetcode刷题】21.三数之和——Java版
  48. 【leetcode刷题】20.最长回文子串——Java版
  49. 【leetcode刷题】19.回文链表——Java版
  50. 【leetcode刷题】18.反转链表——Java版
  51. 【leetcode刷题】17.相交链表——Java&python版
  52. 【leetcode刷题】16.环形链表——Java版
  53. 【leetcode刷题】15.汉明距离——Java版
  54. 【leetcode刷题】14.找到所有数组中消失的数字——Java版
  55. 【leetcode刷题】13.比特位计数——Java版
  56. oracle控制用户权限命令
  57. 三年Java开发,继阿里,鲁班二期Java架构师
  58. Oracle必须要启动的服务
  59. 万字长文!深入剖析HashMap,Java基础笔试题大全带答案
  60. 一问Kafka就心慌?我却凭着这份,图灵学院vip课程百度云