|
Home > Archive > BizTalk Server General > October 2004 > BizTalk 2004 or pure .Net components for request/reply via API:s?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BizTalk 2004 or pure .Net components for request/reply via API:s?
|
|
| Lars Rosenbaum 2004-10-27, 2:47 am |
| My question is: With BizTalk Server 2004 instead of BizTalk Server2002, are
there new reasons to use BizTalk Server for request/reply messages with
response times in the range of 0 to 5 seconds?
We are currently moving from BizTalk 2004 to BizTalk 2002.
In our old projects we only used BizTalk 2002 for asynchronous messages.
For synchronous request / reply messages we used plain .Net
We didnÂīt find any good reasons for using BizTalk 2002 for this,
as we:
1) Only have integration with internally controlled systems (some remote)
2) Usually not file based messages, instead calling APIs via AIC
components and/or Web Services
3) No mappings between message types
Are there new useful reasons in BizTalk 2004 and/or something we missed
already in
BizTalk 2002?
| |
| Scott Woodgate \(MS\) 2004-10-30, 5:48 pm |
| BizTalk Server does add a latency but that latency is typically less than a
second. So the question is if BizTalk takes let's say 1 second what is the
latency of the rest of your programming logic (if it is less than 4 seconds
you are fine).
You should tweak the BizTalk system per the performance whitepaper for
low-latency.
"Lars Rosenbaum" <Lars Rosenbaum@discussions.microsoft.com> wrote in message
news:1137117C-A1AA-49F3-A06C-10F666124B65@microsoft.com...
> My question is: With BizTalk Server 2004 instead of BizTalk Server2002,
are
> there new reasons to use BizTalk Server for request/reply messages with
> response times in the range of 0 to 5 seconds?
>
>
> We are currently moving from BizTalk 2004 to BizTalk 2002.
> In our old projects we only used BizTalk 2002 for asynchronous messages.
> For synchronous request / reply messages we used plain .Net
> We didnīt find any good reasons for using BizTalk 2002 for this,
> as we:
> 1) Only have integration with internally controlled systems (some remote)
> 2) Usually not file based messages, instead calling APIs via AIC
> components and/or Web Services
> 3) No mappings between message types
>
> Are there new useful reasons in BizTalk 2004 and/or something we missed
> already in
> BizTalk 2002?
>
>
>
|
|
|
|
|