If you are confused about Microsoft's Integration Technologies, here is a brief overview of their use-cases:
Integrating applications directly
ASP.NET Web Services (ASMX)
Connecting Windows applications with Windows and non-Windows applications via SOAP
.NET Remoting
Connecting Windows applications with other Windows applications via distributed objects
Enterprise Services
Connecting Windows applications with other Windows applications that use distributed transactions, object lifetime management, etc.
Indigo
Connecting Windows applications with Windows and non-Windows applications using web services, distributed transactions, lifetime management, etc. (subsumes ASMX,.NET Remoting and Enterprise Services)
Integrating applications through queues
Microsoft Message Queuing
Connecting Windows applications with other Windows applications using queued messaging
SQL Service Broker
Connecting SQL Server 2005 applications with other SQL Server 2005 applications using queued messaging
Indigo
Connecting Windows applications with other Windows applications using queued messaging (via MSMQ and/or SSB)
Integrating with applications and data on IBM systems
Host Integration Server 2004
Connecting Windows applications with IBM zSeries and iSeries applications and data
Connecting MSMQ with IBM WebSphere MQ
Integrating applications through a broker
BizTalk Server 2006
Connecting Windows applications and non-Windows applications using diverse protocols
Translating between different message formats
Controlling business processes with graphically-defined orchestrations
Connecting with business partners using industry standards, such as RosettaNet and HL7
Providing business process services, such as Business Activity Monitoring and a Business Rules Engine
Integrating data
SQL Server Integration Services
Combining and transforming data from diverse sources into SQL Server 2005 data
SQL Server Replication
Synchronizing SQL Server data with copies of that data in other instances of SQL Server, Oracle, or DB2
No comments:
Post a Comment