April 2023 Summaries

In 2023, Kong has achieved significant growth by surpassing 600 customers, expanding its employee base, and opening a new office in Singapore, reflecting its focus on both internal expansion and the success of the businesses that utilize its API platform. The company has been recognized as a leader in the Gartner Magic Quadrant for Full Life Cycle API Management, highlighting its comprehensive vision. Kong's cloud-native API management platform, Kong Konnect, has evolved into a unified end-to-end solution, now including the Kong Ingress Controller, offering extensive visibility and control over API gateways. The platform's SaaS control plane has bolstered its appeal, and recent enhancements such as GraphQL support and secure automation emphasize its commitment to innovation. API security remains a priority, with partnerships like the one with Imperva ensuring robust protection against threats. Additionally, Kong is exploring AI's role in API management, with upcoming features in Kong Insomnia aimed at improving developer efficiency. The annual Kong API Summit in September 2023 will serve as a platform to showcase these advancements and foster community engagement.

The article explores various Kubernetes deployment strategies for Kong, focusing on configurations with and without databases and the role of the Kong Ingress Controller in simplifying API exposure on Kubernetes. It highlights the dominance of Kubernetes in container orchestration and discusses the benefits of deploying Kong on Kubernetes, including ease of scaling and flexibility in using databases either within or outside the cluster. The Kong Ingress Controller, which can operate in DB-less mode, allows developers to manage configurations using Kubernetes resources, reducing the need for multiple repositories. The piece further examines scaling strategies, such as running multiple Kong instances, and the introduction of control plane and data plane separation to leverage database features. It also addresses deployments involving multiple Kong Ingress Controllers for namespace isolation and discusses the potential for enhanced reliability through horizontal scaling. The article concludes by suggesting future discussions on resilient architectures and distributed deployments across multiple regions.

API gateways and load balancers are essential tools for optimizing modern web applications, each serving unique yet complementary roles. A load balancer distributes incoming traffic across multiple servers to enhance system responsiveness and reliability, preventing server overload and managing server health. It can perform advanced tasks like HTTPS offloading and content-aware routing, making it invaluable for services supported by multiple servers. On the other hand, an API gateway acts as an intermediary between API consumers and APIs, adding higher-level functionalities such as traffic control, authentication, and metrics collection, which enhance security, observability, and reliability in distributed networks. While API gateways can perform some load balancing tasks, they are not direct substitutes for load balancers. Together, they create a robust architecture that supports growing demands by balancing loads, implementing caching and rate limiting, and collecting detailed usage metrics, improving service quality, security, performance, and reliability.

API proxies, API gateways, and reverse proxies serve distinct purposes in managing and routing web traffic, each with unique functionalities and advantages. An API proxy acts as a mediator between clients and APIs, adding functions like security and caching without altering the API itself, and is suitable for simple enhancements. In contrast, an API gateway provides a comprehensive platform for managing multiple APIs, offering advanced features like full lifecycle management, enhanced security, and improved developer experience, making it ideal for centralized control of APIs. Reverse proxies operate between clients and web servers, handling requests and responses while offering features such as load balancing, caching, and security, and are better suited for general web service management. The choice between these tools depends on specific project requirements, such as the need for API management, security levels, and whether the purpose is to manage APIs specifically or handle broader web traffic.

API management has become a vital aspect of modern software development as it facilitates the effective interaction between software systems by overseeing the lifecycle of application programming interfaces (APIs). This management process includes publishing, monitoring, securing, and analyzing APIs to ensure they deliver value while minimizing issues. Essential components of API management are security features like authentication and encryption, traffic control through rate limiting and load balancing, comprehensive API documentation, and analytics for usage insights. The management system also aids in scalability, security, high availability, and performance monitoring, which are critical for distributed applications. An API management platform typically includes an API gateway for traffic optimization, a developer portal for collaboration and documentation, and analytics tools for monitoring and decision-making. Industry use cases in sectors like FinTech, healthcare, and retail highlight the competitive advantages gained through API management, such as improved security, compliance, and enhanced customer experiences. The transition to microservices architecture underscores the importance of API management, as it supports efficient development, deployment, and operation of APIs, ultimately enabling organizations to focus on delivering core business value.

APIs have become essential in modern software development, enabling seamless communication and data sharing between applications. Effective API monitoring is crucial for ensuring optimal performance and addressing potential issues before they impact users. By implementing comprehensive monitoring strategies, businesses can detect and resolve problems proactively, thereby enhancing user experience and maintaining customer satisfaction. API monitoring involves tracking various performance metrics, identifying patterns from data sources like server logs and user feedback, and ensuring adherence to service-level agreements. This practice not only helps in improving API efficiency and security but also offers deeper insights into user interactions, supporting data-driven decision-making. To set up effective API monitoring, businesses must define objectives, select appropriate tools, configure monitoring systems, set up alerts, and regularly test and adjust their setups to maintain reliability and security.

Cloud migration strategies are evolving to address the challenges of transitioning to the cloud, with a focus on creating a scalable network foundation that supports various migration methods, including lift-and-shift, greenfield development, and re-architecting to microservices. The Crawl/Walk/Run strategy utilizes Kong Konnect and Kong Mesh to provide a robust and flexible network infrastructure to ease the migration process to platforms like Kubernetes or ECS. This approach aims to mitigate risks associated with application modernization by enabling seamless communication between VM-based and cloud-based applications, supporting multi-platform deployments, and offering comprehensive traffic management. The strategy is designed to incrementally build out a network foundation through three phases: Crawl, Walk, and Run, allowing organizations to manage cloud migrations effectively while minimizing disruptions to existing applications. By establishing a distributed mesh network, businesses can focus on innovation while ensuring a reliable and secure migration process, with the flexibility to revert changes if necessary.

An API proxy serves as an intermediary between a client and a backend API, enhancing the API with features like security, caching, and rate limiting without requiring any changes to the API itself. It operates by receiving requests from the client, forwarding them to the backend API, and then returning the responses to the client. Common types of proxies include reverse proxies, SSL proxies, and transparent proxies, each providing distinct functionalities. While API proxies can improve the API's security, caching, and load balancing, they typically offer fewer features compared to API gateways and may introduce challenges such as configuration complexity, performance overhead, and potential security risks. Additionally, AI proxies extend these functionalities to handle AI-specific workflows, optimizing tasks like prompt management and response streaming while reducing development time and cost for organizations using multiple AI models.

A new strategic partnership and resale agreement between Kong and Imperva allows Imperva customers to directly license Kong Enterprise, a leading API management solution, while Kong customers can now utilize the Imperva API Security plugin within Kong Enterprise. This collaboration enables developers to robustly secure APIs and protect business applications and data from unauthorized access by integrating advanced security capabilities into their API development lifecycle. The Imperva API Security plugin provides comprehensive visibility into API calls, risk assessment, and preventative measures against potential attacks without impacting performance. It captures and inspects API calls, ensuring data control remains with the application owner, thereby enhancing security through encryption, authentication, and real-time schema discovery. This joint solution leverages the strengths of both companies to deliver reliable and secure API connections crucial for enterprise customers in the cloud-native era.

Kong has announced the beta release of the Kong Ingress Controller within Kong Konnect at KubeCon + CloudNativeCon Europe 2023, marking its evolution into the first modern unified end-to-end API management platform. This integration provides a comprehensive management system for API gateways, offering seamless visibility and control over edge, cross-application, and in-application APIs, whether deployed as Kubernetes Ingress or via other methods. By merging the features of Kong Gateway with Kubernetes, the Kong Ingress Controller enhances traffic management with functionalities like authentication and caching, and aligns API management with a Kubernetes-centric lifecycle. The platform simplifies the management of Kong Gateways across diverse environments and strengthens governance capabilities, allowing for secure and efficient onboarding for application teams. In addition, the integration activates Kong Konnect's API Portal, API Analytics, and Service Registry, enhancing service management through features like auto-discovery and real-time analytics, thereby centralizing service oversight and optimizing API performance. Users can associate Kong Ingress Controllers with new Runtime Groups via the Runtime Manager, providing a streamlined solution for Kubernetes API management.

Kong has introduced several new features in Kong Konnect to enhance API lifecycle management for the cloud native era, focusing on multi-protocol support, secure automation, service management, and API analytics. Notably, Kong Gateway now includes a GraphQL Rate Limiting plugin that allows for more granular rate limiting based on GraphQL queries, improving flexibility for API clients. The addition of System Accounts enables secure automation by allowing non-personalized accounts, reducing administrative overhead. The Service Hub has been updated to provide a more comprehensive view of services, facilitating easier discovery and management across various environments. Enhanced service documentation, analytic insights, and API specifications are now more accessible, aiding service owners and consumers alike. Additionally, the API analytics interface now supports custom report creation, offering advanced filtering and real-time insights to help maintain API health. These updates aim to streamline API management, making it more efficient and effective for organizations navigating the evolving cloud native landscape.

Kong Mesh and Kuma 2.2 introduces several new enterprise features and improvements, including enhanced UI and policy functionalities, alongside bug fixes. Key upgrades include a new global rate-limiting service requiring an external Redis installation, support for OpenTelemetry in access logs and traces, and the introduction of a "Universal on K8s" deployment mode with Postgres for increased resiliency across multiple regions. The release also features a new MeshLoadBalancing policy for detailed load balancing configurations, improved security with offline token signing, and enhanced RBAC views in the UI. These additions aim to provide users with more flexibility, scalability, and security, while suggesting an easy upgrade process through kumactl or Helm.

Adopting a service mesh, such as Kuma, can significantly simplify and enhance the management of microservices by providing features like mTLS, service discovery, resiliency, and observability without altering the service code or requiring downtime. While transitioning to a service mesh might initially seem to increase complexity, resource usage, and costs, the long-term benefits include streamlined network communication, improved security, and reduced engineering efforts in managing infrastructure. Kuma's user-friendly interface and powerful policy configuration capabilities, such as targetRef-based policies, allow organizations to quickly implement and manage network policies, like retries or traffic filtering, without extensive development or redeployment. Additionally, Kuma offers flexibility by supporting both microservices and classic deployments, enabling organizations to modernize their infrastructure at their own pace and addressing vulnerabilities like the Log4Shell CVE without service interruptions.

Kong Gateway, a widely-used API Gateway, is known for its adaptability to various environments and deployment configurations, requiring careful architectural decisions tailored to specific use cases. The article explores several deployment architectures, each suited to different scenarios, ranging from simple single-instance setups to complex multi-instance distributed systems. A single instance in DB-less mode is ideal for local testing with a declarative configuration file serving as the control plane, while single-instance setups with databases allow for more robust management and plugins. Using decK enables a declarative configuration approach even when a database is involved, although it discourages mixing with direct Admin API changes to maintain predictability. For production environments demanding scalability and fault tolerance, multiple instance deployments provide horizontal scalability and resilience through redundancy. A hybrid deployment allows for secure configurations where data planes may not have direct database access, using persistent connections to propagate configurations from the control plane. This flexibility in deployment options highlights Kong's capability to cater to a wide range of requirements, from development to high-demand production environments.

Kong's API and service mesh platforms are designed to address modern enterprise demands for agility, resilience, and scalability by enabling federated development teams to manage their own APIs while maintaining oversight through a central governance framework. Organizations are increasingly adopting Kong as they transition from traditional API platforms, drawn by its highly flexible deployment options, automation capabilities, and the ability to support both cloud and on-prem environments. Kong's platform offers a 100% declarative approach for predictable API publishing, reducing errors and operational costs, and supports extensive plugin customization to meet specific functional requirements. With a runtime footprint of about 30 MB, Kong delivers high performance and allows for architectural freedom in hybrid and multi-cloud environments. The platform's open-source nature fosters continuous innovation and community engagement, providing numerous plugins that enhance its functionality. Customers report benefits such as improved time to market, lower total cost of ownership (TCO), and enhanced developer productivity.