Akamas can integrate virtually with any pipeline tools to support the ability to optimize systems as part of a Continuous Integration / Continuous Delivery (CI/CD) process.
When integrated into a CI/CD process, Akamas optimization ensures that new releases don't cause incidents due to misconfigured parameters pushed to production without proper review and tuning.
By integrating Akamas into the CI/CD pipeline, you ensure the new release not only passes functional and security tests but also that:
performance regressions in key performance indicators (or SLOs) such as service response time or resource consumption are avoided;
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.
