Preface
There’s no question that we are undergoing a generational shift in computing. With the massive adoption of social media, SaaS, and cloud computing, enterprises are relying more and more on resources beyond the firewall. With this shift, we have seen an explosion in the number of open APIs that are required to interact with these new services. These APIs are key to unlocking the wealth of data and functionality out there. But with this comes serious challenges, with the leading one being integration.
Enterprise application integration (EAI) is a term coined by Gartner, Inc. in 1998 and defined as “the unrestricted sharing of data and business processes among any connected application or data sources in the enterprise.” The challenge is no longer to connect the data sources “within” the enterprise, but instead to connect data sources from a myriad of places, both inside and outside the enterprise.
From Messaging to Connectivity
Typical “Enterprise” message bus and broker implementation’s for integrating on-premise applications are no longer suitable for these Web 2.0 style APIs. I have worked with many of these implementations over the years, including Mule since early in version 2, implementing SOA and message broking solutions and working with technologies and protocols such as SOAP, CORBA, and JMS. However, with this recent shift, it’s less about messaging and more about just staying connected, working natively with Web technologies and protocols such as REST, JSON, and OAuth. ...