In many customer offices, in many countries around the globe, the social engineering process that leads to the right organizational alignment for digital transformation is something that most companies should confront, work through, and, ultimately, embrace.
The rate of change in the API economy is accelerating as more and more organizations understand the power provided by apps and APIs and the agility provided by big data analysis. Here are five changes that will shape the API economy in the coming year.
Our recent webcast entitled “Why APIs are not SOA++” was a popular one. Here are answers to all of the questions and comments you submitted that we didn't have time to address during the presentation.
Although APIs and SOA share similarities, they are designed for very different use cases. In this webcast, Ed Anuff and Dilshad Simons discussed the fundamental differences between API and SOA Governance, how API consumption is different from service exposure, and how a good design pattern at the SOA tier is an anti-pattern at the API tier & vice versa. Discover the advantages of building separate API and services tiers in order to power interactions across all of your digital channels.
In a previous webcast, we established that an SOA is not flexible enough to meet the requirements of today's projects. In this follow-up session, Brian Pagano and Greg Brail talk about what an API initiative that evolves your infrastructure entails - including designing a facade for your services, ensuring services are stateless, handling complex and stateful transactions, and more. Video and slides are here.
In a recent webcast: SOA in the API World - Facades, Transactions, Stateless Services . . . , we talked about what an API initiative to extend SOA with APIs to meet the demands of business in the growing app economy entails - including designing a facade for your services, ensuring services are stateless, handling complex and stateful transactions, and more. There were many great questions posed during our session and we didn't have time to cover all so we've written out the Q&A here.
With enterprises in every industry evolving their IT frameworks to meet the demands of new digital ecosystems and a burgeoning app economy, it's no surprise that we've received questions recently around whether it makes sense to build or buy the components of a Service Oriented Architecture layer. And the answer? Generally not. Obviously, the question of whether one should begin implementing a SOA-based architecture today depends on the particular circumstances of the company's existing technology and its business goals. This article aims to create the beginnings of a decision framework to help those currently facing this type of question.