Cargill Bridges Legacy and Cloud Native with Kong Enterprise
As we continue to expand across new industries and regions, we’re excited to share Cargill’s digital transformation story and how it turned to Kong Enterprise to create a unified API platform across existing legacy and newer cloud native systems. We talked to Jason Walker, senior enterprise architect at Cargill, about their journey to microservices.
What was the driver for Cargill’s move to microservices?
We put Agile, DevOps and CI/CD at the heart of everything we do, and we realized that we needed new tooling to match the new ways we wanted to build products and services. We have a wealth of data from 150 years in business, but we needed to create a simple way for folks to access it and use it to enhance our stakeholders’ experiences. By building an API-first microservices architecture, we knew we could simultaneously provide access to those data and resources and take deployment concerns out of our developers’ workflows.
Why did you choose Kong? What benefits have you seen with Kong?
We wanted to first centralize the platform to make it consistent, then decentralize it to maximize scale, but the legacy API management vendors we looked at weren’t aligned with our vision for decentralization. Kong is lightweight and fast enough to run at the edge, with Kubernetes or in a mesh, which fits our vision perfectly. Together with Kong, we achieve the low latency needed to deploy high-performance, cloud native microservices and the flexibility to seamlessly integrate them across all our systems.
We also wanted to make sure that we were building for scale and enabling the services we built to be re-used across the company, not doing things on a one-off basis. Reusable capabilities need to have one single source of truth, and Kong ensures that all of our constituents are consistent in how they use our services. With Kong, we can just give them a platform-in-a-box that ensures standardization, security and compliance.
With the number of new services we’re adding and creating from decoupling legacy applications into microservices, manually managing our infrastructure would be nearly impossible. Using Kong with Kubernetes allowed us to make decentralization a reality. Kong and Kubernetes let us define how we want our services to behave and then automatically scale the services up or down depending on the situation. The combination of the two allows us to optimize for resource efficiency, resiliency and service availability all in one automated solution.
What results have you seen from implementing Kong?
- Up to 65x faster deployment with automated validations
- 450+ new digital services created in the past six months
- Dynamic infrastructure that auto-scales up and down with demand
What additional plans do you have for using Kong in the future?
It was critical for us that the API platform we chose would allow us to move fast now, but also take us where we want to go. Kong’s view of where the world of software architecture is headed aligns well with ours at Cargill, and we think [Kong] Brain and [Kong] Immunity will really help make that vision a reality.
Want to learn more about Cargill’s digital transformation journey? Read more here!