limiter SpringBoot Edition
Support function：
- Single-machine current limiting
- Cluster Current Limitation
Each time a node is restarted or added, the initial number fills redis, of course, when the capacity is not maximized.
Specific flow restriction parameters, please cooperate with pressure testing tools to optimize, to achieve the QPS you need.
If the current limit is successful, the code block with @LimitTraffic annotation will be executed, otherwise it will not be executed to facilitate user-defined schemes, such as service protection degradation, etc.
In order to improve performance without strong consistency, the maximum current limiting error is -1 cluster number.
<!--Adding dependencies to pom. XML-->
<dependency>
<artifactId>limiter-spring-boot-starter</artifactId>
<groupId>com.github.thierrysquirrel</groupId>
<version>1.0.3-RELEASE</version>
</dependency>## application.properties
spring.redis.host= #Your redis address
spring.redis.port= #The port number of your redis@SpringBootApplication
@EnableLimiter
public class DemoApplication{
public static void main(String[] args){
SpringApplication.run(DemoApplication.class, args);
}
}@TokenLimitedTraffic
public class Hello {
@LimitTraffic(initialQuantity = 2333, maximumCapacity = 3222, addedQuantity = 2333)
public String hello() {
return "world";
}
}@RestController
public class World {
@Resource
private Hello hello;
@GetMapping("/world")
public String world() {
String hello = this.hello.hello();
boolean empty = StringUtils.isEmpty(hello);
if (empty) {
return "service degradation";
}
return hello;
}
}