工作流程是否适合跟踪自动化系统中的大量项目？
Windows 工作流 (WF) 是否适合跟踪仓库中的大量物品？
举例来说，我有一个仓库，每天有 20,000 个包裹在其中移动。这些包裹到达并使用半自动化系统移动到仓库中的 0 到 5 个位置，然后移动到存储位置一段时间。
WF 是一种用于处理跟踪运动和活动的好技术吗？
我听说 WF 对于长时间运行的进程很有用，并且可以相当轻松地将进程移入和移出休眠状态。这些都是很好的功能，让我考虑它。
但是，它似乎通过 WF 应用程序运行单点执行。这不允许大量“运行”活动的包更新它们所在的位置。
我想我喜欢 WF，但我不想尝试让它去做一些它不擅长的事情。
有什么建议吗？
Is Windows Work Flow (WF) good for tracking lots of items in a warehouse?
Say for example I have a warehouse that has 20,000 packages move through it a day. Those packages arrive and move around to 0 to 5 locations in the warehouse using a semi-automated system and then move to a storage location for a while.
Is WF a good technology to use to handle tracking movements and activities?
I hear that WF is good for long running processes and can move process into and out of hybernation fairly easily. These are good features that are getting me to consider it.
However, it seems to run a single point of execution through the WF app. Which would not allow for lots of packages "running" activities to update where they are.
I think I like WF, but I don't want to try to make it work for something that is not its forte.
Any advice?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
听起来您需要为每个动作或长时间运行的流程制定工作流程。
我对你所说的单点执行的含义感到困惑。我会将工作流创建为服务并将其托管在 IIS 或您自己的服务主机中，然后它可以根据您的需要进行扩展。
由于每个移动都是一个工作流程，并且在到达最终目的地的途中有 4 到 5 个停靠点，因此您可以在这些停靠点保留工作流程并从内存中卸载它以帮助扩展。
希望有帮助。
Sounds like you would need a workflow for each movement or long running process.
I'm confused by what you mean by single point of execution. I'd create the workflow as a service and host it in IIS or your own service host and then it can scale as much as you need.
Since each movement would be a workflow, and there are 4 to 5 stops along the way to its final destination, you could persist the workflow at those stopping points and unload it from memory to help with the scaling.
Hope that helps.