You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
893 B
893 B
| title | date | draft | opensource | topics |
|---|---|---|---|---|
| 5 principles for deploying your API from a CI/CD pipeline | 2019-07-26T00:00:00+02:00 | false | [3scale] | [API Management] |
At Red Hat, we strongly believe an API is not “just another piece of software.” Instead, we think an API is a software component in conjunction with:
An interface to communicate with it. An ecosystem of consumers that communicate with this software. A relationship with developers consuming this API. An API is built, deployed, and managed not just with the usual methods; as a result, deploying your API from a CI/CD pipeline requires additional processes, tools, and skills.
In this article, we will focus on the overarching principles and key steps to deploy your API from a CI/CD pipeline.