任务队列和异步接口的正确打开方式(.NET Core版本)
任务队列和异步接口的正确打开方式
什么是异步接口?
Asynchronous Operations
Certain types of operations might require processing of the request in an asynchronous manner (e.g. validating a bank account, processing an image, etc.) in order to avoid long delays on the client side and prevent long-standing open client connections waiting for the operations to complete. For such use cases, APIs MUST employ the following pattern:
For POST requests:
Return the
202 AcceptedHTTP response code.In the response body, include one or more URIs as hypermedia links, which could include:
- The final URI of the resource where it will be available in future if the ID and path are already known. Clients can then make an HTTP
GETrequest to that URI in order to obtain the completed resource. Until the resource is ready, the final URI SHOULD return the HTTP status code404 Not Found.
{ "rel": "self", "href": "/v1/namespace/resources/{resource_id}", "method": "GET" }- A temporary request queue URI where the status of the operation may be obtained via some temporary identifier. Clients SHOULD make an HTTP
GETrequest to obtain the status of the operation which MAY include such information as completion state, ETA, and final URI once it is completed.
{ "rel": "self", "href": "/v1/queue/requests/{request_id}, "method": "GET" }"- The final URI of the resource where it will be available in future if the ID and path are already known. Clients can then make an HTTP
For PUT/PATCH/DELETE/GET requests:
Like POST, you can support PUT/PATCH/DELETE/GET to be asynchronous. The behaviour would be as follows:
Return the
202 AcceptedHTTP response code.In the response body, include one or more URIs as hypermedia links, which could include:
- A temporary request queue URI where the status of the operation may be obtained via some temporary identifier. Clients SHOULD make an HTTP
GETrequest to obtain the status of the operation which MAY include such information as completion state, ETA, and final URI once it is completed.
{ "rel": "self", "href": "/v1/queue/requests/{request_id}, "method": "GET" }"- A temporary request queue URI where the status of the operation may be obtained via some temporary identifier. Clients SHOULD make an HTTP
APIs that support both synchronous and asynchronous processing for an URI:
APIs that support both synchronous and asynchronous operations for a particular URI and an HTTP method combination, MUST recognize the Prefer header and exhibit following behavior:
- If the request contains a
Prefer=respond-asyncheader, the service MUST switch the processing to asynchronous mode. - If the request doesn't contain a
Prefer=respond-asyncheader, the service MUST process the request synchronously.
It is desirable that all APIs that implement asynchronous processing, also support webhooks as a mechanism of pushing the processing status to the client.
资料引自:paypal/API Design Patterns And Use Cases:asynchronous-operations
用人话来说
简单来说就是请求过来,直接返回对应的resourceId/request_id,然后可以通过resourceId/request_id查询处理结果
处理过程可能是队列,也可能直接是异步操作
如果还没完成处理,返回404,如果处理完成,正常返回对应数据
好像也没什么讲了....
全文结束吧.
样例代码部分啦
实现逻辑
创建任务,生成"request-id"存储到对应redis zset队列中
同时往redis channel发出任务消息, 后台任务处理服务自行处理此消息(生产者-消费者模式)
任务处理服务处理完消息之后,将处理结果写入redis,request-id为key,结果为value,然后从从redis zset从移除对应的"request-id"
获取request-id处理结果时:如果request-id能查询到对应的任务处理结果,直接返回处理完的数据; 如果request-id还在sortset队列则直接返回404 + 对应的位置n,表示还在处理中,前面还有n个请求;
时序图大概长这样:

喜闻乐见代码时间
RequestService.cs
// RequestService.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;
using CorrelationId;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Logging;
using Newtonsoft.Json.Linq;
using StackExchange.Redis;
using static StackExchange.Redis.RedisChannel;
namespace MTQueue.Service
{
public class RequestService
{
private readonly ICorrelationContextAccessor _correlationContext;
private readonly ConnectionMultiplexer _redisMultiplexer;
private readonly IServiceProvider _services;
private readonly ILogger<RequestService> _logger;
public RequestService(ICorrelationContextAccessor correlationContext,
ConnectionMultiplexer redisMultiplexer, IServiceProvider services,
ILogger<RequestService> logger)
{
_correlationContext = correlationContext;
_redisMultiplexer = redisMultiplexer;
_services = services;
_logger = logger;
}
public long? AddRequest(JToken data)
{
var requestId = _correlationContext.CorrelationContext.CorrelationId;
var redisDB = _redisMultiplexer.GetDatabase(CommonConst.DEFAULT_DB);
var index = redisDB.SortedSetRank(CommonConst.REQUESTS_SORT_SETKEY, requestId);
if (index == null)
{
data["requestId"] = requestId;
redisDB.SortedSetAdd(CommonConst.REQUESTS_SORT_SETKEY, requestId, GetTotalSeconds());
PushRedisMessage(data.ToString());
}
return redisDB.SortedSetRank(CommonConst.REQUESTS_SORT_SETKEY, requestId);
}
public static long GetTotalSeconds()
{
return (long)(DateTime.Now.ToLocalTime() - new DateTime(1970, 1, 1).ToLocalTime()).TotalSeconds;
}
private void PushRedisMessage(string message)
{
Task.Run(() =>
{
try
{
using (var scope = _services.CreateScope())
{
var multiplexer = scope.ServiceProvider.GetRequiredService<ConnectionMultiplexer>();
multiplexer.GetSubscriber().PublishAsync(CommonConst.REQUEST_CHANNEL, message);
}
}
catch (Exception ex)
{
_logger.LogError(-1, ex, message);
}
});
}
public Tuple<JToken, long?> GetRequest(string requestId)
{
var redisDB = _redisMultiplexer.GetDatabase(CommonConst.DEFAULT_DB);
var keyIndex = redisDB.SortedSetRank(CommonConst.REQUESTS_SORT_SETKEY, requestId);
var response = redisDB.StringGet(requestId);
if (response.IsNull)
{
return Tuple.Create<JToken, long?>(default(JToken), keyIndex);
}
return Tuple.Create<JToken, long?>(JToken.Parse(response), keyIndex);
}
}
}
// RedisMQListener.cs
using System;
using System.Text;
using System.Threading;
using System.Threading.Tasks;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;
using Microsoft.Extensions.Logging;
using Microsoft.Extensions.Options;
using MTQueue.Model;
using MTQueue.Service;
using Newtonsoft.Json.Linq;
using StackExchange.Redis;
using static StackExchange.Redis.RedisChannel;
namespace MTQueue.Listener
{
public class RedisMQListener : IHostedService
{
private readonly ConnectionMultiplexer _redisMultiplexer;
private readonly IServiceProvider _services;
private readonly ILogger<RedisMQListener> _logger;
public RedisMQListener(IServiceProvider services, ConnectionMultiplexer redisMultiplexer,
ILogger<RedisMQListener> logger)
{
_services = services;
_redisMultiplexer = redisMultiplexer;
_logger = logger;
}
public Task StartAsync(CancellationToken cancellationToken)
{
Register();
return Task.CompletedTask;
}
public virtual bool Process(RedisChannel ch, RedisValue message)
{
_logger.LogInformation("Process start,message: " + message);
var redisDB = _services.GetRequiredService<ConnectionMultiplexer>()
.GetDatabase(CommonConst.DEFAULT_DB);
var messageJson = JToken.Parse(message);
var requestId = messageJson["requestId"]?.ToString();
if (string.IsNullOrEmpty(requestId))
{
_logger.LogWarning("requestId not in message.");
return false;
}
var mtAgent = _services.GetRequiredService<ZhihuClient>();
var text = mtAgent.GetZhuanlan(messageJson);
redisDB.StringSet(requestId, text.ToString(), CommonConst.RESPONSE_TS);
_logger.LogInformation("Process finish,requestId:" + requestId);
redisDB.SortedSetRemove(CommonConst.REQUESTS_SORT_SETKEY, requestId);
return true;
}
public void Register()
{
var sub = _redisMultiplexer.GetSubscriber();
var channel = CommonConst.REQUEST_CHANNEL;
sub.SubscribeAsync(channel, (ch, value) =>
{
Process(ch, value);
});
}
public void DeRegister()
{
// this.connection.Close();
}
public Task StopAsync(CancellationToken cancellationToken)
{
// this.connection.Close();
return Task.CompletedTask;
}
}
}
// RequestsController.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;
using CorrelationId;
using Microsoft.AspNetCore.Mvc;
using MTQueue.Service;
using Newtonsoft.Json.Linq;
namespace MTQueue.Controllers
{
[Route("v1/[controller]")]
[ApiController]
public class RequestsController : ControllerBase
{
private readonly ICorrelationContextAccessor _correlationContext;
private readonly RequestService _requestService;
private readonly ZhihuClient _mtAgentClient;
public RequestsController(ICorrelationContextAccessor correlationContext,
RequestService requestService, ZhihuClient mtAgentClient)
{
_correlationContext = correlationContext;
_requestService = requestService;
_mtAgentClient = mtAgentClient;
}
[HttpGet("{requestId}")]
public IActionResult Get(string requestId)
{
var result = _requestService.GetRequest(requestId);
var resource = $"/v1/requests/{requestId}";
if (result.Item1 == default(JToken))
{
return NotFound(new { rel = "self", href = resource, method = "GET", index = result.Item2 });
}
return Ok(result.Item1);
}
[HttpPost]
public IActionResult Post([FromBody] JToken data, [FromHeader(Name = "Prefer")]string prefer)
{
if (!string.IsNullOrEmpty(prefer) && prefer == "respond-async")
{
var index = _requestService.AddRequest(data);
var requestId = _correlationContext.CorrelationContext.CorrelationId;
var resource = $"/v1/requests/{requestId}";
return Accepted(resource, new { rel = "self", href = resource, method = "GET", index = index });
}
return Ok(_mtAgentClient.GetZhuanlan(data));
}
}
}
完整代码见:https://github.com/liguobao/TaskQueueSample
任务队列和异步接口的正确打开方式(.NET Core版本)的更多相关文章
- C++11随机数的正确打开方式
C++11随机数的正确打开方式 在C++11之前,现有的随机数函数都存在一个问题:在利用循环多次获取随机数时,如果程序运行过快或者使用了多线程等方法,srand((unsigned)time(null ...
- iOS开发小技巧--相机相册的正确打开方式
iOS相机相册的正确打开方式- UIImagePickerController 通过指定sourceType来实现打开相册还是相机 UIImagePickerControllerSourceTypeP ...
- Xcode 的正确打开方式——Debugging(转载)
Xcode 的正确打开方式——Debugging 程序员日常开发中有大量时间都会花费在 debug 上,从事 iOS 开发不可避免地需要使用 Xcode.这篇博客就主要介绍了 Xcode 中几种能 ...
- C#语法——泛型的多种应用 C#语法——await与async的正确打开方式 C#线程安全使用(五) C#语法——元组类型 好好耕耘 redis和memcached的区别
C#语法——泛型的多种应用 本篇文章主要介绍泛型的应用. 泛型是.NET Framework 2.0 版类库就已经提供的语法,主要用于提高代码的可重用性.类型安全性和效率. 泛型的定义 下面定义了 ...
- InnoDB缓冲池预加载在MySQL 5.7中的正确打开方式
InnoDB缓冲池预加载在MySQL 5.7中的正确打开方式 https://mp.weixin.qq.com/s/HGa_90XvC22anabiBF8AbQ 在这篇文章里,我将讨论在MySQL 5 ...
- Console控制台的正确打开方式
Console控制台的正确打开方式 console对象提供了访问浏览器调试模式的信息到控制台 -- Console对象 |-- assert() 如果第一个参数断言为false,则在控制台输出错误信息 ...
- (一)Redis for Windows正确打开方式
目录 (一)Redis for Windows正确打开方式 (二)Redis for 阿里云公网连接 (三)Redis for StackExchange.Redis 下载地址 官网.中文网1 及 中 ...
- List的remove()方法的三种正确打开方式
转: java编程:List的remove()方法的三种正确打开方式! 2018年08月12日 16:26:13 Aries9986 阅读数 2728更多 分类专栏: leetcode刷题 版权声 ...
- Pull Request的正确打开方式(如何在GitHub上贡献开源项目)
Pull Request的正确打开方式(如何在GitHub上贡献开源项目) GitHub的官方帮助如下: Fork A Repo: https://help.github.com/articles/f ...
随机推荐
- c++ 基类,派生类的类型兼容性
#include <iostream> using namespace std; class CFather { public: void display() const { cout&l ...
- P3174 [HAOI2009]毛毛虫
题目描述 对于一棵树,我们可以将某条链和与该链相连的边抽出来,看上去就象成一个毛毛虫,点数越多,毛毛虫就越大.例如下图左边的树(图 1 )抽出一部分就变成了右边的一个毛毛虫了(图 2 ). 输入输出格 ...
- php反序列化
之前听漏洞银行的一个女生讲php反序列化.她说了一句.php反序列话找public变量. 导致我以为必须php反序列化.可控的变量必须是public or protected.private私有的变量 ...
- AI-Info-Micron:用内存解决方案演化神经网络智能
ylbtech-AI-Info-Micron:用内存解决方案演化神经网络智能 1.返回顶部 1. 用内存解决方案演化神经网络智能 我们的大脑每天会进行数千次极其复杂的操作.无论是提醒我们小心被炉子烫到 ...
- 26、springboot与消息
概述: 1.大多应用中,可通过消息服务中间件来提升系统异步通信.扩展解耦能力消息服务中两个重要概念: 2.消息代理(message broker)和目的地(destination) ...
- 2019.3.6 Github学习 &Git学习
Github学习 1.使用Github 1.1 目的 借助github托管项目代码 1.2 基本概念 仓库(Repository) 仓库的意思是:即你的项目,你想在Github上开源一个项目,那就必须 ...
- linux下批量重命名文件
# 使用通配符批量创建 多个文件:$ touch zqunor{1..7}.txt # 批量将多个后缀为 .txt 的文本文件重命名为以 .c 为后缀的文件:$ rename 's/\.txt/\.c ...
- ASP.NET Core AD 域登录 (转载)
在选择AD登录时,其实可以直接选择 Windows 授权,不过因为有些网站需要的是LDAP获取信息进行授权,而非直接依赖Web Server自带的Windows 授权功能. 当然如果使用的是Azure ...
- PDO介绍(16)
安装PDO PDO的数据选项 链接到数据库服务器并选择数据库 错误处理 获取和设置属性 查询执行 准备语句介绍 获取数据 设置绑定列 处理事务
- No MyBatis mapper was found in '[com.wuji.springboot]' package. Please check your configuration
No MyBatis mapper was found in '[com.wuji.springboot]' package. Please check your configuration. 这个原 ...