The question is: cloud, on-premises or hybrid?
The value of a holistic API management solution is clear, but how to deploy the components can be a dilemma.
When customers look at implementing API management solutions, they often look at them from a holistic viewpoint – seeing how the complete solution addresses the needs of the enterprise.
And frankly, that makes sense. It’s important to look at the entire package and ensure all needs are met. To do less would almost certainly result in a poor or failed implementation.
However, when it comes to deployment, an additional view of the selected API management solution is warranted.
CA is sponsoring a webinar on March 1 at 9 a.m. PST that discusses the secondary view to consider with API management deployment issues. Read on for a preview of what we’ll discuss. There is still time to register.
A second look
All successful API management solutions today are comprised of an API gateway, some form of management, some form of API development/deployment (preferably through a developer portal), and to make it all a worthwhile endeavor, some form of service/data consumption (likely through a mobile app).
Holistically, one sees an API management solution harmoniously at work. In reality, you can see that there are really two phases taking place here:
And they raise some interesting questions: where should an enterprise deploy a design-time solution vs a runtime solution?
Design-time is where the enterprise introduces and maintains the business relationship with the app developer and provides the tools for the developer to use to consume an API (i.e. documentation, tutorials, samples, code generation). That tool is typically a Developer Portal. But the question then becomes, where should the portal be deployed – on-premises? In the cloud? The answer really depends. Consider this:
Runtime involves an API gateway that is providing API data and services such as data transformation, composition, routing, and traffic control. It’s also likely providing security, and it’s where important analytical elements of the API lifecycle are taking place, such as health tracking, performance/workflow monitoring, and reporting.
The question again is where to deploy the gateway – on-premises or in the cloud? And again, the answer is “it depends.”
We invite you to attend our webinar learn more about API management deployment options, and take a brief look at microservices patterns and their impact on API management deployment. Please make sure you register.