Last post Jun 27, 2011 02:27 PM by ajitsunny
Jun 27, 2011 11:06 AM|banshi|LINK
I am building a web app for which I need a bit of guidance in design. We have one application from vendor which uses SQL Server 2005 as database. Let’s say vendor’s application provides details on Order etc.
The web app that I am building will have its own database (SQL Server 2005). For my application to get any details about “Orders”, it needs to go thru BizTalk. So the flow would as below
Jun 27, 2011 01:26 PM|atconway|LINK
If you were speaking directly in reference to ASP.NET only, then I think ample guidance could be provided. But since you threw BizTalk into the mix, I suggest you might want to thy their forums for this type of question:
BizTalk Server MSDN Forums:
If you do have some ASP.NET only questions or in reference to the ASP.NET architecture, please feel free to elaborate so more help can be provided.
Jun 27, 2011 02:27 PM|ajitsunny|LINK
You can use Service Broker feature of SQL Server 2005/2008 for smooth database to database communication. Best part is that use of costly Biztalk server can be removed, asynchronous data communication can be established between databases, and it is a completely
service oriented pattern used by SQL Server for communication which also having complete queue management system.
It is generally known as Service Oriented Database Architecture (SODA).
How SQL Server 2005 Enables Service-Oriented Database Architectures