The Kong and Amazon (AWS) partnership is stronger than ever! As Kong continues to evolve, with Kong Konnect and Kong Mesh, the means of integrating with AWS grows as well. In a continuous effort to offer cutting-edge collaborations, Kong announces new Amazon Elastic Kubernetes Service (EKS) based contributions: Kong Konnect AddOns for the EKS Blueprints for Terraform framework and two new Kong AWS workshops.

Domain-driven designs are popular in organizations that have complex domain models and wish to organize engineering around them. REST-based architectures are a common choice for implementing the API entry point into these domains. REST-based solutions are straightforward for the API builder and for API consumers concerned with data from a single API. But what about developers tasked with aggregating information across domains?

In the ever-evolving landscape of digital business operations, staying ahead of the curve requires constant adaptation and innovation. Kong Mesh 2.4 contains several enhancements to help your organization’s infrastructure be more efficient. In this blog post, we’ll explore the key benefits of Kong Mesh 2.4 across three critical domains: security, resilience, and flexibility.

Few things are more frustrating than encountering a product with either no documentation or worse: documentation that leads you astray. When it comes to developing APIs, schemas typically define how requests and responses are formatted and guide how clients and services exchange data. Commonly, schemas aren’t used to generate documentation or software development kits (SDKs), allowing them to become stale and inaccurate.

With our AWS partnership, we jointly created two Kong Konnect AWS EKS Terraform Blueprints AddOns — eks-blueprint-konnect-runtime-instance and eks-blueprint-konnect-kic — to help bootstrap your Kong Konnect instances on EKS. In this post, we’ll discuss what AWS EKS Blueprints AddOns for Terraform are and their benefits, plus we’ll demo the Kong Konnect AddOns we’ve built out.

While JSON-based APIs are ubiquitous in the API-centric world of today, many industries adapted internet-based protocols for automated information exchange way before REST and JSON became popular. One attempt to establish a standardized protocol suite for automated data interchange within and between enterprises was SOAP, originally an acronym for Simple Object Access Protocol.

This post is part of a series on becoming a secure API-first company. For a deeper dive, check out the eBook Leading Digital Transformation: Best Practices for Becoming a Secure API-First Company. The growth of APIs isn’t just rapid — it’s a seismic shift. Industry insiders say they plan to introduce more APIs in the next five years than all the APIs they’ve created up until today. And this impending surge will place a serious burden on mission-critical API infrastructure.

Since our last Kong Ingress Controller release, we’ve been working hard, and today we’re pleased to announce the immediate availability of Kong Ingress Controller 2.11. KIC 2.11’s standout feature is “last known good configuration”, which allows you to scale your data planes out even if you have a broken configuration on your Kubernetes API server. That’s a strange sentence to write, but it happens more than you’d think.

Building APIs is a craft. Your API product must be stable, accurate, well documented, performant, and meet the informational demands of your clients — no small task. In this series, we’ll take a close look at GraphQL, a trending API technology that aims to help you deliver efficient and capable APIs. GraphQL’s unique and nuanced view of the client-server relationship offers interesting benefits for API delivery.

Perhaps the most exciting feature introduced in Kong Gateway in recent years is the addition of WebAssembly support. WebAssembly (or Wasm) was originally developed to bring additional languages beyond JavaScript into the browser. However, nothing stops it from being used in the backend as well! With WebAssembly in Kong Gateway, you’ll be able to build and deploy Wasm filters using languages such as Rust and Go, and configure filter chains to operate on your Kong routes and services.