Kong’s Wanny Morellato and Deepak Mohandas recently joined Justin and Autumn on [the ShipIt podcast](https://changelog.com/shipit/93)the ShipIt podcast to talk hybrid infrastructure with Kong Gateway and Kong Mesh. They unravel the complexities of hybrid infrastructure at scale, discussing the processes, strategies, and philosophies that drive continuous delivery, infrastructure as code, and more.
In a rapidly evolving digital landscape, businesses face the daunting challenge of managing diverse infrastructure environments efficiently. Kong Gateway and Kong Mesh emerge as stalwart solutions, empowering organizations to navigate this complexity with confidence and agility.
From orchestrating seamless communication across microservices to ensuring robust security and governance, Kong Gateway and Kong Mesh serve as the linchpins of modern infrastructure architecture.
In this episode, Wanny and Deepak take you on a journey through the intricate processes that enable continuous delivery, emphasizing the importance of automation, monitoring, and iterative development. Whether it’s deploying new features or rolling out updates, they decipher the strategies that keep organizations ahead of the curve in today’s fast-paced digital ecosystem.
They also dissect the concept of infrastructure as code, a paradigm shift that revolutionizes the way we manage and provision resources. Through real-world examples and insightful discussions, they demystify the intricacies of declarative configuration and infrastructure automation, empowering listeners to harness its transformative power effectively.
Whether you’re a seasoned veteran or a curious newcomer, head over to [the ShipIt podcast](https://changelog.com/shipit/93)the ShipIt podcast and check it out!
Traffic patterns shape architectural boundaries and understanding them clearly reveals why different tools are necessary. North-south traffic flows between external clients and your services, crossing the network perimeter in the process. Common e
[](https://konghq.com/blog/enterprise/the-difference-between-api-gateways-and-service-mesh)
Imagine you have a single Service, order-api . You want to apply a strict rate limit to most traffic, but you want to bypass that limit—or apply a different one—if the request contains a specific X-App-Priority: High header. Previously, you had t
[](https://konghq.com/blog/engineering/conditional-policy-execution)
How OAuth 2.0 Token Exchange Reshapes Trust Between Services — and Why the API Gateway Is Exactly the Right Place to Enforce It Modern applications don’t run as a single monolithic. They are composed of services — frontend APIs, backend microservi
[](https://konghq.com/blog/engineering/token-exchange-at-the-gateway)
Traditional APIs are, in a word, predictable. You know what you're getting: Compute costs that don't surprise you Traffic patterns that behave themselves Clean, well-defined request and response cycles AI APIs, especially anything that runs on LLMs
[](https://konghq.com/blog/engineering/monetize-ai-apis)
Running Kong in front of your Solace Broker adds real benefits: Authentication & Access Control – protect your broker from unauthorized publishers. Validation & Transformation – enforce schemas, sanitize data, and map REST calls into event topics.
[](https://konghq.com/blog/engineering/smarter-event-driven-apis-kong-solace)
Architecture Overview A multicloud DCGW architecture typically contains three main layers. 1\. Konnect Control Plane The SaaS control plane manages configuration, plugins, and policies. All gateways connect securely to this layer. 2\. Dedicated C
[](https://konghq.com/blog/engineering/dedicated-cloud-gateways-managed-redis-multi-cloud)
The example below shows how an AI agent can be built using Volcano SDK with minimal code, while still interacting with backend services in a controlled way. The agent is created by first configuring an LLM, then defining an MCP (Model Context Prot
[](https://konghq.com/blog/engineering/secure-ai-agents-volcano-sdk-kong-mcp-proxy)