SOA

This guest post, written by Andy Thurai, originally appeared on Infosecurity.com. Andy is the Chief Architect & Group CTO for the Intel unit responsible for Cloud/ Application security, API, Big Data, SOA and Mobile middleware solutions. You can follow him on Twitter at @AndyThurai.

In 2013, Learning how to enable your business with APIs is a common theme among enterprise IT departments and also among business. Enterprises are seeing that the current state of SOA Governance is headed towards extinction. These enterprises face a new kind of tension: the app and API economies on the one hand, where enterprises drive new revenue streams by (gulp) publishing corporate data APIs for third-party developers to use, and SOA on the other, where tight governance is the name of the game. But the loose coupling in RESTful web services forces a discipline all its own.

On Friday, Part I of this series covered the broad strokes of what is one of the integration spaces’ pivotal annual gatherings, Gartner’s Application, Architecture Delivery and Integration Summit (AADI). This show sets the coming year’s tone for application integration at Fortune 500 companies, and to a degree for the integration space as a whole. At the last two shows, that tone has been spelled out clearly: A-P-I.

Last week was a good one for APIs in Las Vegas. Gartner brought together the enterprise architecture and integration crowd for its annual Application Architecture Delivery & Integration Summit.  The annual show focused on corporate app development and the integration/API/SOA space is something central to the mobility challenges of today’s enterprise.