It is the age of automation where everyone tries to minimize manual steps while building software. API management is no exception. The term "CI/CD," which expands to "Continous Integration/ Continous Deployment," is the more technical term for this automation process. According to this definition, it contains a 2-step process for automating your software development and delivery.
- Continuous Integration — This means that whenever you make a change to your source code, it needs to be well tested before integrating into the existing stable codebase.
- Continuous Deployment — This means that once the integration tests have passed, the deployment of the new piece of code to the relevant environments (staging, prod) needs to happen automatically as part of the build process.
When it comes to the development of enterprise software, enterprise architects design the software in such a manner that entire software system breaks down into several layers (layered architecture). The back end services, which implement the business logic, are developed with a general-purpose programming language and the help of existing frameworks. Implementing a CI/CD process on top of this kind of approach is quite straightforward since it is easier to write unit tests using the same programming language, and source code can be managed in a GitHub repository. With a tool like TravisCI, you can easily integrate the integration and deployment process together when there is a change in the source code.
from DZone.com Feed https://ift.tt/2tE5WV4
No comments:
Post a Comment