简体   繁体   English

将Amazon SNS与ServiceStack集成

[英]Integrating Amazon SNS with ServiceStack

I'm developing a suite of ETL-style apps which will link cloud-based systems with on-premise systems using Amazon SNS and Amzazon SQS along with some restful services. 我正在开发一套ETL风格的应用程序,它将基于云的系统与使用Amazon SNSAmzazon SQS的内部部署系统以及一些宁静的服务相连接。 SNS allows you to set-up an HTTP endpoint as a subscriber and your apps can publish messages to SNS which will be dispatched to your HTTP endpoint (as a json message), as well as an SQS queue, email, sms etc. SNS允许您将HTTP端点设置为订阅者,并且您的应用可以将消息发布到SNS,SNS将被分派到您的HTTP端点(作为json消息),以及SQS队列,电子邮件,短信等。

What I would like to do is handle the HTTP response from my on-premise app which already incorporates some parts of the servicestack framework. 我想要做的是处理来自我的内部应用程序的HTTP响应,该应用程序已经包含了servicestack框架的某些部分。 However most of the documentation for servicestack and other restful frameworks describes their usage in a typical request/response pattern. 但是,servicestack和其他restful框架的大多数文档都描述了它们在典型请求/响应模式中的用法。 But in this case i'm only waiting for a response from SNS. 但在这种情况下,我只是在等待SNS的回应。 Can I still use any servicestack code for handling response only messages? 我仍然可以使用任何servicestack代码来处理仅响应消息吗?

Amazon SNS pushes the notifications to your app using a regular POST request, you can handle it like any other incoming POST request. Amazon SNS使用常规POST请求将通知推送到您的应用程序,您可以像处理任何其他传入POST请求一样处理它。

The endpoint is just a regular url in your app that will receive the POST requests in JSON format . 端点只是您应用中的常规URL,它将以JSON格式接收POST请求。

Webhook is just a fancy name, don't get confused by that. Webhook只是一个奇特的名字,不要被它弄糊涂。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM