- This topic has 1 reply, 1 voice, and was last updated 9 years, 1 month ago by
.
-
Posts
-
-
Hi
Our application uses a bunch of web services, such as
Authentication Service, Authorization Service, Data Service etc.
These web services are used by our web/windows applications.
We would like to start using Biztalk in our enterprise.
\”Don’t use a hammer if all you need is a pat.\”
Would it be best approach to convert each web service to its respective orchestration,
for ex: AuthenticationOrchestration, AuthorizationOrchestration, DataOrch etc.
If we follow this approach would we end up with a hammer.Also, is it better to use biztalk orchestrations only for long running tasks and not for short running request/response tasks. For ex: If we want to authenticate and authorize a user in web/windows application, then have the web service do it rather than have a orchestration as it is a short request/response task.
Any input is much appreciated.
Thanks. -
While Biztalk is capable of providing the request/response services, I would tend not to use it to replace your existing services.
The first question – [b:d041bf9fe0]is there any value added by using an orchestration[/b:d041bf9fe0].
In the case of authentication and authorisation the answer is probably not.
The data service may be different, do you aggregate data from different sources, do you update multiple data repositories, do these updates need to be co-ordinated, do all data repositories support DTC transactions or do you have to implememt compensating logic for failuresWhile Biztalk is great at solving some problems it is not the answer for everything.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.