• November 7, 2019

5 reasons to use APIIDA API Gateway Manager in your release process

Providing new and updated services for customers is an ever-changing process. To meet the increasing expectations from customers in new and better services, different ways evolved in the past years. Different approaches, like DevOps or Continuous Integration/Continuous Deployment, needs to be considered from every company. APIIDA API Gateway Manager has the goal to help customers with different challenges with the Layer7 API Gateway from Broadcom (formally CA API Gateway). In this blog post the author will present you 5 reasons, why a company with Layer7 API Gateways should use APIIDA API Gateway Manager in their release process.

1. Zero Downtime and Deliver Fast

For many companies APIs are a central element for success, and therefore zero downtime is a duty. It costs a lot of money every minute the platform is unavailable. While there will always be bugs that escape quality assurance, the downtime caused by manual errors in the release process or trivial bugs needs to be close to zero.

APIIDA API Gateway Manager automates a lot of the day-to-day operations and makes them fool proof. Our product helps to standardise pre-defined release steps, to reduce the dependency on key people.

2. Automation and CI/CD pipeline

Building a pipeline for CI/CD to automate a release process is necessary to speed up the deployment process. Building a pipeline with build-in tools, like GMU, is hard to achieve, due to a lot of manual steps to be done. The APIIDA API Gateway Manager can be added to any CI/CD solution as it provides a REST-based API and a corresponding command line tool to start migrations from other tools. If no CI/CD tool is used in the company, APIIDA provides an own pipeline utility to automate migrations. 

3. Moving into cloud

Migration into a cloud setup for Layer7 API Gateways are a reasonable step to decrease operational costs and have a more scalable infrastructure. APIIDA can help in this process by providing vast knowledge. APIIDA API Gateway Manager features its own REST-based API to cope with dynamic scaling. As the product is based on Docker itself, it can be installed in the cloud, on-premise or in hybrid scenarios. 

4. Static analysis of services and dependencies 

Analysis, which dependencies are needed to be updated need to be done directly in development. If this was forgotten, this can result in unnoticed bugs. The APIIDA API Gateway Manager can check in the migration for missing elements and notify the operator before the actual migration. Also, if the internal IDs are different between source and target gateway cluster, the migration might fail by using GMU. The gateway manager can automatically detect this and propose a proper mapping. 

This reduces issues before testers or end users get involved and therefore improves efficiency of the whole process.


5. Develop on local gateways, deploy on network gateways

The APIIDA API Gateway Manager supports private gateways of developers (e.g. local virtual appliance) by cloning an existing gateway to the gateway from the developer. The development can be done locally and therefore the efficiency will increase, due to higher speed and no connection issues. Migration back to a testing or QA gateway will only migrate changed assets. This enables multi developer support and mitigates conflicts.

Get started. Now.

2021_APIIDA_Internetseite_Illustrationen_Footer 01