任务队列和异步接口的正确打开方式

什么是异步接口?

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 Accepted HTTP 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 GET request to that URI in order to obtain the completed resource. Until the resource is ready, the final URI SHOULD return the HTTP status code 404 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 GET request 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" }"

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 Accepted HTTP 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 GET request 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" }"

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-async header, the service MUST switch the processing to asynchronous mode.
  • If the request doesn't contain a Prefer=respond-async header, 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版本)的更多相关文章

  1. C++11随机数的正确打开方式

    C++11随机数的正确打开方式 在C++11之前,现有的随机数函数都存在一个问题:在利用循环多次获取随机数时,如果程序运行过快或者使用了多线程等方法,srand((unsigned)time(null ...

  2. iOS开发小技巧--相机相册的正确打开方式

    iOS相机相册的正确打开方式- UIImagePickerController 通过指定sourceType来实现打开相册还是相机 UIImagePickerControllerSourceTypeP ...

  3. Xcode 的正确打开方式——Debugging(转载)

    Xcode 的正确打开方式——Debugging   程序员日常开发中有大量时间都会花费在 debug 上,从事 iOS 开发不可避免地需要使用 Xcode.这篇博客就主要介绍了 Xcode 中几种能 ...

  4. C#语法——泛型的多种应用 C#语法——await与async的正确打开方式 C#线程安全使用(五) C#语法——元组类型 好好耕耘 redis和memcached的区别

    C#语法——泛型的多种应用   本篇文章主要介绍泛型的应用. 泛型是.NET Framework 2.0 版类库就已经提供的语法,主要用于提高代码的可重用性.类型安全性和效率. 泛型的定义 下面定义了 ...

  5. InnoDB缓冲池预加载在MySQL 5.7中的正确打开方式

    InnoDB缓冲池预加载在MySQL 5.7中的正确打开方式 https://mp.weixin.qq.com/s/HGa_90XvC22anabiBF8AbQ 在这篇文章里,我将讨论在MySQL 5 ...

  6. Console控制台的正确打开方式

    Console控制台的正确打开方式 console对象提供了访问浏览器调试模式的信息到控制台 -- Console对象 |-- assert() 如果第一个参数断言为false,则在控制台输出错误信息 ...

  7. (一)Redis for Windows正确打开方式

    目录 (一)Redis for Windows正确打开方式 (二)Redis for 阿里云公网连接 (三)Redis for StackExchange.Redis 下载地址 官网.中文网1 及 中 ...

  8. List的remove()方法的三种正确打开方式

    转: java编程:List的remove()方法的三种正确打开方式! 2018年08月12日 16:26:13 Aries9986 阅读数 2728更多 分类专栏: leetcode刷题   版权声 ...

  9. Pull Request的正确打开方式(如何在GitHub上贡献开源项目)

    Pull Request的正确打开方式(如何在GitHub上贡献开源项目) GitHub的官方帮助如下: Fork A Repo: https://help.github.com/articles/f ...

随机推荐

  1. Odoo权限控制

    转载请注明原文地址:https://www.cnblogs.com/cnodoo/p/9278734.html 一:Odoo中的权限设置主要有以下5种 1)菜单.报表的访问权限 Odoo可以设置菜单项 ...

  2. Ajax请求与浏览器缓存

    在现代Web应用程序中,前端代码充斥着大量的Ajax请求,如果对于Ajax请求可以使用浏览器缓存,那么可以显著地减少网络请求,提高程序响应速度. 1. Ajax Request 使用jQuery框架可 ...

  3. SpringBoot实战(二)之计划任务

    计划任务这个对于Java开发者们,应该不陌生了,非常常用又非常常见.比如jdk自带的Timer 实现例子如下: class MyTask extends TimerTask{ @Override pu ...

  4. 关于CUDA C 项目中“ error C2059: 语法错误:“<” ”问题的解决方法

    该问题的关键在于理解CUDA项目中C\C++文件需要由c++编译器进行编译,而CUDA C的源文件需要由CUDA的编译器nvcc.exe进行编译. 发生该语法错误的原因是cu文件被C++编译器所编译, ...

  5. python——reuqests模块使用pip安装始终不成功

    使用pip install xxx 来安装某一库. 使用 pip uninstall xxx 来卸载. 而pip 的也可以采用常见的两种安装方法 在centos系列下 使用sudo yum insta ...

  6. PAT——1073. 多选题常见计分法(20)

    批改多选题是比较麻烦的事情,有很多不同的计分方法.有一种最常见的计分方法是:如果考生选择了部分正确选项,并且没有选择任何错误选项,则得到50%分数:如果考生选择了任何一个错误的选项,则不能得分.本题就 ...

  7. JNI由浅入深_9_JNI 异常处理

    1 .本地代码中如何缓存和抛出异常 下面的代码中演示了如何声明一个会抛出异常的本地方法.CatchThrow这个类声明了一个会抛出IllegalArgumentException异常的名叫doit的本 ...

  8. 在Eclipse中执行、配置Hadoop

    版权全部: zhe-jiang.he@hp.com  严禁转载! 1.安装插件 准备程序: eclipse-3.3.2(这个版本号的插件仅仅能用这个版本号的eclipse) hadoop-0.20.2 ...

  9. C++的前置++、后置++和前置--、后置--

    一.C++的前置++和后置++ 在C++中,运算符重载是你必须要掌握的重点,而前置++和后置++有什么区别呢?其实前置++和后置++是有关于 影响效率的问题,前置++比后置++的效率要高,原因是因为前 ...

  10. Centos7下python3.7的pipSSLError问题

    在Centos7下成功安装了python3.7, 但是在使用pip3的时候出现了以下错误 中间试过了网上大家给出的好多种办法,一开始我只是在编译的时候 ./configure --with-ssl(p ...