请建议 .Net 作业/任务队列
我需要建立一个处理数据的服务网络。 每个服务都需要自己的任务队列。 首先，我需要 QueueTask、CancelTask、StopTask、GetTaskStatus 和 GetTaskProgress 等操作。
我正在寻找任务队列的框架或完全构建的实现。
此时我知道一些选项：
MSMQ - 它可以满足我的需求，但需要太多编码来支持。
Castle.Sheduling - 调度解决方案。 它提供了可插入的触发器，我可以实现它来满足我的需求。 然而编码仍然太多。
ServiceBUS - 例如MassTransit。 但是，我不确定它们如何支持长队列并且仍然需要管道代码。
理想的解决方案是提供任务队列托管的框架。 这将能够重新启动而不会丢失任务。 可以通过网络访问它，例如作为 SOAP 端点。
问题实际上是你用什么，为什么？ 您建议使用什么？
I need to build a network of services that will process data. Each service needs its own task queue. Preliminary I will need operations like QueueTask, CancelTask, StopTask, GetTaskStatus and GetTaskProgress.
I am looking for framework or fully built implementation of Task Queue.
At this time I know some options:
MSMQ - It OK for my needs, but require too much coding for support.
Castle.Sheduling - Scheduling solution. It provides pluggable Trigger, which I could implement to achive my needs. However still too many coding.
ServiceBUS - for example MassTransit. However, I am not sure how they support long queues and still require plumbing code.
An ideal solution will be framework that will provide hosting of task queue. That will be able to restart without loosing tasks. That will be accessible from network for example as SOAP end-point.
The question is actually what do you use, why? What do you suggest to use?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
嗯，听起来好像您必须编写一些管道，尤其是通过 SOAP 将任务队列公开给外界。
我建议查看：
两者都是 .NET 框架和 MSMQ 上的开源服务总线实现。
Hmm, it sounds as though you are going to have to write some plumbing, especially to expose the task queues to the outside world via SOAP.
I'd suggest looking at:
Both are open source service bus implemenations on the .NET framework and MSMQ.
还有来自 Apache 组织的 ActiveMQ。 它有很多良好的跨平台/语言支持，而且是免费的！
在商业领域，还有 Tibco EMS，它具有良好的 Java/C#绑定
There's also ActiveMQ from the Apache organizations. It's got lots of good cross platform/language support and is free!
In the commercial sector there's also Tibco EMS which has good Java/C# bindings
也许您正在寻找类似 CONTROL-M 的东西？
http://en.wikipedia.org/wiki/CONTROL-M
Maybe you're looking for something like CONTROL-M?
http://en.wikipedia.org/wiki/CONTROL-M
嗯，我也许正在经历类似的过程。 抱歉，这不是一个答案，但也许是从上下文的角度来看。
我遇到的情况是，网络应用程序允许用户上传设计图像。问题是我需要显然处理初始上传，但然后对图像的实际处理进行排队。 例如，我需要：
同样，我立刻想到了我以前在金融领域工作时使用的 MSMQ 和 IBM-MQseries，并且因为我使用的是 SQL 2008 R2，所以我注意到它也有（可能有一段时间！）排队机制。
所以我在同一条船上试图找到正确的选择！
感谢到目前为止的回复..将查看一些解决方案，但同样，任何其他想法将不胜感激
Well I am perhaps going through a similar process. Sorry, this isn't an answer as such, however maybe from a contextual perspective.
I have a situation where a web app will allow a user to upload images for a design.. the problem is I need to obviously handle the initial upload, but then queue the actual process of the images. For instance, I need to:
Again, I instantly thought MSMQ from my old days working in finance along with IBM-MQseries, and because I am using SQL 2008 R2, I notice it too has (probably for a while!) queuing mechanisms.
So I am sort of in the same boat trying to find the correct option!
Thanks for the replies so far.. will check out some of the solutions, but again, any other ideas would be grateful