一个Http接收位置和多个业务流程绑定到它。 [英] One Http Receive location and Multiple Orchestration Bound to it.

问题描述

大家好，

我有一个名为A的基本应用程序。它只有HTTP类型的接收位置。

I have a base application called A. It only has a Receive Location of HTTP type.

我有N个不同的应用程序，它们具有HTTP类型的接收位置。我已将应用程序A的引用添加到这N个应用程序中的每个应用程序，并将我的N个编排绑定到应用程序AI中的单个接收位置已尝试使用相同的接收位置命中不同的orchs并且它工作正常。

I have N different applications which have the receive location of HTTP type. I have added the reference of the Application A to each of these N applications and bound my N orchestrations to only the single receive location in Application A.I have tried hitting different orchs using the same receive location and it works fine.

我想知道这种架构的优点和主要缺点是什么。请提供宝贵的建议。

I want to know what are the pros and mainly cons of this type of the architecture. Please provide your valuable suggestions.

谢谢。

问候，

Mandar Dharmadhikari

Mandar Dharmadhikari

推荐答案

缺点是因为N个应用程序依赖于您的应用程序A.

the cons is that the since the N applications are dependant on your Application A.

如果你想更新应用程序A，我的意思是如果你想重新部署，你必须首先在所有那些提到的N个应用程序中删除这个应用程序A引用。

if you want to update Application A, i mean if you want to redeploy , you have to first remove this Application A reference in all those referred N applications.

专业人员是您已经体验过的，您可以在任何其他应用程序中使用。

And pros is you already experienced, you can use in any other applications.

这篇关于一个Http接收位置和多个业务流程绑定到它。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！