ESB 架构中什么是长期存在的业务流程？
我正在阅读有关 EIP 和 ESB 的内容，我看到了有关轻量级 ESB 与独立 ESB 的文章。
“轻量级 ESB 的主要缺点是无法实现复杂、长期存在的业务流程。这使得它们不适合企业自上而下的 BPM 方法。除了这些限制之外，这些轻量级解决方案还以更简单的方式涵盖了所有重复出现的集成需求。这是可能的，因为它们是围绕集成最佳实践和约定构建的。”
那么什么是“长寿的业务流程”呢？你能给我举个例子吗？
I am reading about EIP and ESB, i saw article about lightweight ESB vs stand alone ESB.
"The main lack with lightweight ESBs is the impossibility to implement complex, long-living, business processes. That makes them inappropriate for an Enterprise top-down BPM approach. This limitation apart these light solutions cover all recurring integration requirements, in a more simple way. This is possible because they are built around integration best practices and conventions."
So what is "long-living business processes"? Can you give me examples?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当业务流程从开始到结束跨越数小时、数天或数周（等）时，它被视为长期存在的流程。因此，流程将具有跨时间的特定状态。当 ESB 轻量级时，需要删除一些功能，例如消息持久性和某些服务编排功能（不像业务流程引擎那么复杂，但达到了知名的水平）等级。）
When a business process spans hours, Days, or weeks (etc.) from start to finish it is considered as a Long living process. So the process will have a certain state which span across time.When the ESB is light weight it is needed to drop some of the functionality such as message persistance and certain service orchestration features (Not as complex as Business process Engine but up to a reputed level.)