Improving Developer Happiness with GitOps

At Helvetia, deploying a new API took months of manual coordination. Now, developers do it themselves with a single pull request.

#1about 8 minutes

How business strategy drives the need for integration

Helvetia's strategic focus on customer ecosystems and omnichannel experiences creates a strong business case for improving API integration capabilities.

#2about 6 minutes

Overcoming the friction of manual API deployment

Exposing REST APIs traditionally involves significant friction due to manual coordination between development, security, and network teams, leading to long delays.

#3about 7 minutes

Building a resilient and scalable API gateway

The integration platform uses an API gateway with a decoupled control and data plane architecture, allowing for resilient and low-latency deployments close to backend services.

#4about 5 minutes

Adopting a GitOps workflow for API management

Using a Git repository as the single source of truth, API configurations are managed through a pull request workflow that automates provisioning across multiple systems.

#5about 3 minutes

How to define and subscribe to APIs as code

API producers and consumers use a declarative YAML format, based on OpenAPI v3 specs, to define services and manage subscriptions within the Git repository.

#6about 5 minutes

Automating governance and validation with PR checks

The GitOps process automatically validates API definitions for correctness, semantics, and security compliance during the pull request, providing instant feedback to developers.

#7about 5 minutes

Boosting developer happiness and the future of self-service

This self-service model empowers developers and reduces cycle time, with future plans to fully automate approvals and extend the GitOps pattern to other resources like Kafka and S3.