Applications running on Amazon Web Services (AWS), one of the most widely used platforms in the cloud, generate a lot of APIs in need of management. At the Amazon Web Services (AWS) re:Invent 2013 conference yesterday, Axway announced that the Axway API Gateway is now available on the AWS cloud platform. The availability of the Axway API Gateway via the AWS Marketplace is a sign of the growing maturity of the AWS cloud environment, Mark O’Neill, Axway vice president of innovation, says.
AWS has become home to thousands of applications that are routinely invoked via APIs.
The challenge, of course, is not just making sure the right API is being invoked by the right application, but also ensuring the governance polices needed to make those APIs secure are in place. In the rush to foster the development of the API economy, API management fundamentals are often overlooked, O’Neill says.
The Axway API Gateway is not likely to be the only API management platform on AWS; over time, the Axway API Gateway will also show up on other cloud computing platforms, O’Neill says. In fact, it’s reasonable to assume there will be tight integration between, for example, instances of the Axway API Gateway in the cloud and instances of the same API management platform running on a private cloud with VMware, he says. The goal is to make it easier to dynamically allocate additional resources in the cloud if the demand for data being invoked via a particular API should suddenly spike.
Organizations must be able to apply a consistent set of management and governance policies across both public and private clouds, says O’Neill. These policies may wind up being the same ones that are in place around internal applications that leverage traditional Web services technologies such as SOAP. The Axway API Gateway prevents islands of APIs by making it easier to consistently apply management policies across multiple application integration scenarios, he says.
APIs are all the rage in Web 2.0 applications, which are typically customer-facing. However, IT organizations have massive investments in business-to-business (B2B) applications based on software-oriented architectures (SOAs), and these must be integrated with Web 2.0 applications that usually support business-to-consumer (B2C) business processes. The issue is finding a way for these different application paradigms to get along as the line between B2B and B2C applications continues to blur.