Java中的线程(六)- Guarded Suspension 模式

什么是Guarded Suspension 模式

该模式是一种保护模式,其核心是仅有服务可以提供服务的时候才提供服务,比如双十一期间,很多用户进行付账,客户端的请求数超过了服务器的即时处理能力,而服务端不能丢弃任何客户请求,此时最佳的方案就是让客户端的请求进行排队,服务端一个一个的处理。这样,既保证了所有的客户端请求不丢失,同事也避免了服务器由于同时处理太多的请求崩溃。此场景也和平时我们去银行办理业务类似,每次去就那么几个窗口,办理的客户太多了,那么能做的就是拿号排队。
结构图


参与者

角色作用
Request 客户端请求
RequestQueue保护请求的队列
ClientThread客户端进程
ServerThread服务端进程

代码实现


(1)Request
public class Request {
private String name;
public Request(String name){
this.name = name;
}
public String getName(){
return name;
}
public String toString() {
return "[Request "+name+" ]";
}
}
(2)ClientThread
public class ClientThread extends Thread{
private ConcurrentLinkedQueue<Request> requestQueue;
public ClientThread(ConcurrentLinkedQueue<Request> requestQueue,String name) {
super(name);
this.requestQueue = requestQueue;
}
public void run() {
for (int i = 0; i < 10; i++) {
Request request = new Request("RequestID "+i+" Thread_Name:"+Thread.currentThread().getName());
System.out.println(Thread.currentThread().getName()+" requests "+request);
requestQueue.add(request);
try {
Thread.sleep(10);
} catch (InterruptedException e) {
}
System.out.println("ClientThread Name is :"+Thread.currentThread().getName());
}
System.out.println(Thread.currentThread().getName()+" request end");
}
}
(3) ServerThread
public class ServerThread extends Thread{


private ConcurrentLinkedQueue<Request> requestQueue;
public ServerThread(ConcurrentLinkedQueue<Request> requestQueue,String name){
super(name);
this.requestQueue = requestQueue;
}
public void run() {
while(true){
Request request = requestQueue.poll();
try {
Thread.sleep(100);
} catch (InterruptedException e) {
}
System.out.println(this.getName()+" handler "+request);
}
}
}
(4)Main
public class Test {
public static void main(String[] args) {
ConcurrentLinkedQueue<Request> requestQueue = new ConcurrentLinkedQueue<Request>();
for (int i = 0; i < 10; i++) {
new ServerThread(requestQueue, "ServerThread "+i).start();
}
for (int i = 0; i < 10; i++) {
new ClientThread(requestQueue, "ClientThread"+i).start();
}
}
}
结果:
...
ClientThread Name is :ClientThread3
ClientThread3 request end
ClientThread Name is :ClientThread7
ClientThread7 request end
ClientThread Name is :ClientThread2
ClientThread2 request end
ClientThread Name is :ClientThread9
ClientThread9 request end
ClientThread Name is :ClientThread8
ClientThread8 request end
ClientThread Name is :ClientThread5
ClientThread5 request end
ClientThread Name is :ClientThread1
ClientThread Name is :ClientThread4
ClientThread4 request end
ClientThread1 request end
ClientThread Name is :ClientThread0
ClientThread0 request end
ClientThread Name is :ClientThread6
ClientThread6 request end
ServerThread 1 handler [Request RequestID 0 Thread_Name:ClientThread5 ]
ServerThread 3 handler [Request RequestID 0 Thread_Name:ClientThread6 ]
ServerThread 2 handler [Request RequestID 0 Thread_Name:ClientThread3 ]
ServerThread 0 handler [Request RequestID 0 Thread_Name:ClientThread1 ]
ServerThread 4 handler [Request RequestID 0 Thread_Name:ClientThread0 ]
ServerThread 5 handler [Request RequestID 0 Thread_Name:ClientThread7 ]
ServerThread 6 handler [Request RequestID 0 Thread_Name:ClientThread4 ]
ServerThread 7 handler [Request RequestID 0 Thread_Name:ClientThread8 ]
ServerThread 9 handler [Request RequestID 0 Thread_Name:ClientThread9 ]
ServerThread 8 handler [Request RequestID 0 Thread_Name:ClientThread2 ]
ServerThread 3 handler [Request RequestID 1 Thread_Name:ClientThread2 ]
ServerThread 2 handler [Request RequestID 1 Thread_Name:ClientThread5 ]
ServerThread 4 handler [Request RequestID 1 Thread_Name:ClientThread4 ]
ServerThread 0 handler [Request RequestID 1 Thread_Name:ClientThread6 ]
ServerThread 5 handler [Request RequestID 1 Thread_Name:ClientThread3 ]
ServerThread 1 handler [Request RequestID 1 Thread_Name:ClientThread0 ]
ServerThread 6 handler [Request RequestID 1 Thread_Name:ClientThread7 ]
ServerThread 7 handler [Request RequestID 1 Thread_Name:ClientThread1 ]
ServerThread 8 handler [Request RequestID 1 Thread_Name:ClientThread9 ]
ServerThread 9 handler [Request RequestID 1 Thread_Name:ClientThread8 ]
ServerThread 0 handler [Request RequestID 2 Thread_Name:ClientThread5 ]
ServerThread 1 handler [Request RequestID 2 Thread_Name:ClientThread6 ]
ServerThread 5 handler [Request RequestID 2 Thread_Name:ClientThread4 ]
ServerThread 4 handler [Request RequestID 2 Thread_Name:ClientThread1 ]
ServerThread 6 handler [Request RequestID 2 Thread_Name:ClientThread2 ]
...



  • 0
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
Java设计模式是一组经过实践验证的面向对象设计原则和模式,可以帮助开发人员解决常见的软件设计问题。下面是常见的23种设计模式: 1. 创建型模式(Creational Patterns): - 工厂方法模式(Factory Method Pattern) - 抽象工厂模式(Abstract Factory Pattern) - 单例模式(Singleton Pattern) - 原型模式(Prototype Pattern) - 建造者模式(Builder Pattern) 2. 结构型模式(Structural Patterns): - 适配器模式(Adapter Pattern) - 桥接模式(Bridge Pattern) - 组合模式(Composite Pattern) - 装饰器模式(Decorator Pattern) - 外观模式(Facade Pattern) - 享元模式(Flyweight Pattern) - 代理模式(Proxy Pattern) 3. 行为型模式(Behavioral Patterns): - 责任链模式(Chain of Responsibility Pattern) - 命令模式(Command Pattern) - 解释器模式(Interpreter Pattern) - 迭代器模式(Iterator Pattern) - 介者模式(Mediator Pattern) - 备忘录模式(Memento Pattern) - 观察者模式(Observer Pattern) - 状态模式(State Pattern) - 策略模式(Strategy Pattern) - 模板方法模式(Template Method Pattern) - 访问者模式(Visitor Pattern) 4. 并发型模式(Concurrency Patterns): - 保护性暂停模式Guarded Suspension Pattern) - 生产者-消费者模式(Producer-Consumer Pattern) - 读写锁模式(Read-Write Lock Pattern) - 信号量模式(Semaphore Pattern) - 线程模式(Thread Pool Pattern) 这些设计模式可以根据问题的特点和需求来选择使用,它们提供了一些可复用的解决方案,有助于开发高质量、可维护且易于扩展的软件系统。
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值