Systems | Development | Analytics | API | Testing

The promise of agentic AI is clear: autonomous systems that can reason, plan, and act on your behalf. But there's a fundamental problem standing between that vision and enterprise reality: agents need context to make decisions, and that context lives scattered across your organization. Context is any data — or any abstraction that enables access to data — that an agent needs to do its job. Customer records in your CRM. Inventory levels behind your fulfillment APIs.

We're very excited to announce Kong Mesh 2.12 to the world! Kong Mesh 2.12 delivers two very important features: SPIFFE / SPIRE support, which provides enterprise-class workload identity and trust models for your mesh, as well as a consistent Kuma Resource Identifier (KRI) naming convention for resources in the Mesh. Read on to learn more!

The word on the street is that Ambient Mesh is the obvious evolution of service mesh technology — leaner, simpler, and less resource-intensive. But while Ambient Mesh is an exciting development, the reality is more nuanced. It is more than likely that a sidecar-based mesh is still a better fit for your workload and organization.

We’re at it again, bringing more incremental improvements to Kong Mesh!

The latest version of Kong Mesh brings an improved provisioning experience and streamlined management of policies — plus user interface enhancements to elevate your experience deploying and managing Kong Mesh. Built on top of Kuma, Kong Mesh is a service mesh designed to provide security, observability, and traffic control across modern, distributed applications.

The focus of this blog is to provide step-by-step instructions for deploying and configuring Kong Mesh with Kong Konnect on an AWS ECS instance so that anyone will be able to get pre-production installation of Kong Mesh standing up on their own.

Container technologies are always evolving — and we're not talking Tupperware here. Over the past years, service mesh has emerged as a crucial component for managing complex, distributed systems. As organizations increasingly adopt Kubernetes for orchestrating their containerized applications, understanding how to effectively implement and utilize a service mesh within this environment becomes paramount.

A service mesh is a mechanism for managing communications between the various individual services that make up modern applications in a microservice-based system. When a service mesh is applied, all inter-service communication is routed through proxies, which can be used to implement networking features such as encryption and load balancing.

As a developer working with microservices architectures, you may find yourself facing numerous challenges. Managing multiple services, each with its own potential points of failure, can be complex. Issues such as communication difficulties, security concerns, and lack of visibility are common in these environments. These challenges are not unique. As microservices architectures expand, they often introduce complexities that can be demanding for development teams to handle.