Back in Chapter 7, Planning Service-oriented BizTalk Solutions, we looked at Message Exchange Patterns (MEP) and evaluated differences between them. We concluded that asynchronous patterns can be more service-oriented and loosely coupled than synchronous patterns. However, there are cases where you want a single business process to accommodate invocation by either mechanism. In certain scenarios, the caller has no interest in the outcome, but in other situations, the caller requires resolution about the service outcome. You could choose to build two distinct processes that each support a distinct MEP, but this is fairly inefficient and challenging to maintain. What if we want to build a BizTalk orchestration with the least amount of effort required that can be invoked either synchronously or asynchronously?
SOA Patterns with BizTalk Server 2013 and Microsoft Azure
By :
SOA Patterns with BizTalk Server 2013 and Microsoft Azure
By:
Overview of this book
Table of Contents (21 chapters)
SOA Patterns with BizTalk Server 2013 and Microsoft Azure Second Edition
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
Building BizTalk Server 2013 Applications
Windows Communication Foundation Primer
Using WCF Services in BizTalk Server 2013
REST and JSON Support in BizTalk Server 2013
Azure BizTalk Services
Azure Service Bus
Planning Service-oriented BizTalk Solutions
Schema and Endpoint Patterns
Asynchronous Communication Patterns
Orchestration Patterns
Versioning Patterns
Frameworks and Tools
New SOA Capabilities in BizTalk Server 2013 – Azure Hybrid Patterns
What's New and What's Next?
Index
Customer Reviews