Process automation is no longer the domain of large-scale business processes but an integral part of modern application architecture. This books shows you where the two meet., In the previous post of the series, I described how messages can be transmitted from a sender application to intended receiver applications through Messaging Channels, and how the Azure Integration Services can be leveraged to implement these Enterprise Integration Patterns. Messaging Endpoints are the application touch points that abstract the application internals and can be used to either , Standardized interfaces let you integrate a new backend system with Application Integration in less time, thereby reducing the development time. Integration Connectors also handle API upgrades and maintenance, thereby reducing the cost of maintenance. Security Integration Connectors support various authentication types, ensuring secure connections., On-premises connectors provide access to on-premises systems such as SQL Server, SharePoint Server, SAP, Oracle DB, file shares, and others. Integration account connectors help you transform and validate XML, encode and decode flat files, and process business-to-business (B2B) messages using AS2, EDIFACT, and X12 protocols., Structure the connecting middleware between these applications as a Message Bus that enables them to work together using messaging. A Message Bus is a combination of a common data model, a common command set, and a messaging infrastructure to allow different systems to communicate through a shared set of interfaces., The following resources can also help you design your application. Besides providing general information about an integration mechanism or process, each article helps you select an Azure service that best meets your need for that area. Asynchronous messaging options: Understand various types of messages and the entities that participate in a messaging infrastructure. Choose between virtual .