Integrating with pipelines

Akamas can integrate virtually with any pipeline tools to support the ability to optimize systems as part of a Continous Integration / Continous Delivery (CI/CD) process.

When integrated into a CI/CD process, the Akamas optimization becomes an additional step that can ensure a new version that is being released will not cause incidents due to bad configurations pushed to production that nobody has time to look at and that can require adjustments to make the new release perform best.

By integrating Akamas in the CI/CD pipeline, it is possible to also ensure the new release is not only passing functional and security tests but also that:

• performance regressions with respect to previous builds are avoided, such as regressions with respect to some key performance indicators (or SLOs) such as service response time or resource consumption;

Reactive optimization: in-the-pipe remediation (optimization task is triggered by quality gate)

• configuration settings are properly tailored for the new release, thus avoiding configuration bottlenecks (e.g. wrong JVM settings or smaller Kubernetes pod resources for the new release) and decreasing the risk of performance or availability incidents.

Proactive optimization in-the-pipe