A simple definition of MABS is many services loosely coupled together to achieve an SOA pattern. The requirement for installation and maintenance of the services is delegated to Microsoft Azure.

Let us start by considering how we might architect the traditional EAI view from Chapter 1, Building BizTalk Server 2013 Applications. A message can be received by the source and passed on to a bridge. The source might be FTP, SFTP, a Service Bus Queue or a Service Bus Topic. Alternatively, the bridge can receive a message directly via an HTTP Post. The bridge is where all pre-processing and data transformations take place before publishing the message to a Service Bus Topic or Queue. Pipelines and maps perform the same task in BizTalk Server. The Service Bus performs the same function that MessageBox fulfils for BizTalk Server; namely, it queues messages until each subscriber gets the message. The publish-subscribe functionality comes in two forms: a queue with one subscription...