March 2022 Summaries

Exceptional digital customer experiences are crucial for business success, with customer-obsessed companies seeing significantly higher revenue growth and retention. APIs are central to creating these experiences, necessitating a reliable API management vendor like Kong, which offers a next-generation solution with significantly faster and higher throughput compared to traditional vendors like Apigee. Kong's platform is designed for complex, modern architectures such as microservices and multi-cloud environments, offering flexibility and minimal need for technology replacements, earning it recognition in the Gartner Magic Quadrant. Kong also distinguishes itself with superior customer support, connecting clients to expert teams swiftly for efficient troubleshooting, unlike Apigee, which relies on less specialized support channels. Additionally, Kong's lightweight gateway supports high-volume, low-latency API connectivity, ensuring seamless user experiences, while its modular architecture simplifies both initial deployment and ongoing operations.

In the first installment of a three-part series, the blog explores the challenges and opportunities presented by the next wave of digital innovation, focusing on Web3, the metaverse, and enhanced connectivity. As businesses brace for rapid advancements, the importance of seamless application connectivity through APIs is emphasized as crucial for achieving digital transformation. The 2022 API & Microservices Connectivity Report highlights growing concerns among technology leaders about competitive displacement due to lagging innovation, with many predicting dire outcomes within a few years if they fail to adapt. The text identifies major hurdles such as reliance on outdated technologies, lack of IT automation, and skills shortages exacerbated by the Great Resignation. To stay ahead, companies must invest in modern tools and improve developer efficiency, focusing on application security, performance, and the ability to adopt new technologies. These efforts aim to enhance the developer experience, which in turn is expected to lead to improved customer satisfaction and business success. The series promises further insights into how businesses can empower their developer teams to drive innovation in future installments.

In the final part of a series on APIs, sustainability, and climate change, the text explores the environmental impact of common architectural trends and provides recommendations to mitigate it. The shift from monolithic systems to microservices is highlighted as a popular transformation that improves resource efficiency, yet increases network traffic, which can be managed through appropriate protocols like gRPC and service mesh technologies. The text advocates for event-driven architectures (EDA) over synchronous RESTful APIs to reduce wasted energy from idle API polls, promoting the use of pub/sub patterns for asynchronous processing. Additionally, it argues for an API-first integration approach to minimize idle resource consumption compared to point-to-point integrations, emphasizing the importance of managing APIs through a gateway for auditing and optimization. The author calls for the acknowledgment of IT's role in global energy consumption and urges readers to adopt green engineering principles in their technology practices to combat climate change.

Matt Klein, a software engineer at Lyft and creator of the open-source project Envoy, shares insights from his career and views on technology trends in a recent Q&A. Envoy, a service proxy for cloud-native applications, is notable for its successful community-driven development, paralleling the challenges faced by startups in terms of building a supportive and functional community. Klein highlights his admiration for the Windows NT kernel as a standout project in terms of software quality and emphasizes the importance of community ethos in open-source projects. He discusses the promising potential of Rust as a programming language and reflects on Envoy's API longevity and the complexities of transitioning between its versions. Klein also explores the early-stage development of WebAssembly and the evolving landscape of service meshes, suggesting a shift toward platform-based solutions that abstract away underlying technologies like Kubernetes and Envoy. He expresses interest in projects like Dapr, which aim to simplify cloud-native application development by providing standardized APIs, and envisions a future where these technologies become invisible implementation details.

In this Kongcast episode, Josh Long, a Spring Developer Advocate at VMware, discusses the evolution and impact of the Spring framework on Java application development, emphasizing the role of Spring Boot in the microservices boom around 2014/2015. He explains how Spring facilitated a shift from monolithic to more modular, agile architectures, with tools like Spring Boot and Spring Native contributing to this transformation. The conversation touches on the integration of Spring with modern technologies like Kubernetes and GraalVM, highlighting how these advancements allow for faster, more efficient application deployment and execution. Long also elaborates on the innovations within Spring Native, which leverage GraalVM to compile Java applications into native binaries, significantly reducing startup times and resource consumption while maintaining Java's dynamic capabilities. The episode underscores Spring's ongoing adaptability and influence in the software development landscape, particularly in cloud and serverless environments.

TBC Bank in Georgia has partnered with Kong to enhance its API ecosystem by leveraging Kong's API management platform, which offers API Gateway, lifecycle management, consulting services, and staff training. This strategic collaboration aims to simplify daily operations, improve customer service, and foster technological transformation through efficient, decentralized API management. By selecting Kong, TBC intends to introduce the concept of "API as a product," enhancing innovation cycles and bridging legacy and modern systems. The partnership is expected to refine TBC's digital service delivery, improve developer efficiency, and positively impact banking products and services, contributing to Georgia's technological ecosystem and international image.

APIs are instrumental in promoting sustainability and addressing climate change by enabling businesses to integrate green technologies and optimize operations. They play a dual role by allowing companies to both build and consume APIs, which can lead to reduced carbon emissions and more sustainable practices. Companies such as Patch and Shopify utilize APIs for carbon offsetting, enabling businesses to calculate and mitigate their emissions. Innovation in climate tech is thriving, as seen with Tomorrow.io, which offers hyperlocal weather forecasts through APIs, helping organizations like airlines optimize fuel usage and enhance climate resilience. Uplight exemplifies how APIs can help utilities optimize energy use, reduce CO2 emissions, and save costs. The growing API economy is not only a response to consumer demand for sustainability but also a strategic business decision, encouraging companies to leverage technological advancements to create impactful green solutions.

The blog post explores the complexities of building robust APIs in the context of microservices, focusing on the three most popular API development approaches: REST, gRPC, and GraphQL. REST, the most widely used architecture, benefits from its alignment with HTTP protocols, making it familiar to most developers, though it can produce bloated responses for complex resources. gRPC, designed by Google, is noted for its efficiency and suitability for low-powered clients like IoT devices, but it lacks browser support and has a steeper learning curve. GraphQL, known for its query precision, allows clients to request specific data fields, reducing payload sizes but increasing server-side complexity and caching difficulty. The post emphasizes that no single API model fits all scenarios, and the choice depends on specific application requirements, suggesting that a combination of these models could be used within the same system to meet diverse needs effectively.

In the modern microservices landscape, deploying services efficiently requires a strategic approach involving infrastructure orchestration, application deployment, and service publishing. This detailed guide demonstrates using Kubernetes-in-Docker (Kind) for infrastructure, Pulumi for orchestration, and Kong API Gateway for service publishing. Kong functions as a reverse proxy and ingress controller, offering features like authentication, rate limiting, and traffic monitoring to enhance agility and centralized management. Pulumi, an Infrastructure as Code platform, supports a collaborative software engineering process across various programming languages. The step-by-step instructions guide users through setting up their environment, deploying a Kong API Gateway, and testing it with a sample application. The guide provides insights into setting up Kubernetes namespaces, certificates, secrets, and Helm charts, establishing a robust foundation for further exploration and development with Kong. This setup lays the groundwork for future use in the DevMyOps series and offers a practical approach for evaluating and developing with Kong locally.

Microservices architecture offers significant advantages over traditional monolithic designs by allowing for independent deployment and scaling of services, resulting in increased system resilience, faster delivery of changes, and more efficient hardware usage. Continuous Integration (CI) and Continuous Delivery (CD) are crucial for realizing these benefits, facilitating rapid release cycles and reducing the time to deliver value to users. CI originated from eXtreme Programming and aims to minimize code integration issues, while CD moves builds through the deployment pipeline toward production readiness. Adopting a DevOps culture, which integrates development and operations responsibilities, enhances the effectiveness of CI/CD processes by breaking down silos and treating infrastructure as code. Microservices also introduce the complexity of managing multiple pipelines, which can be mitigated by using containerization to standardize and streamline deployment processes. Continuous Deployment extends CD by automating the final push to production, contingent on robust automated testing and monitoring strategies that facilitate rapid response to issues. Ultimately, these practices enable organizations to deliver incremental improvements, obtain user feedback, and enhance product quality through agile and iterative development processes.

Speed to market and innovation are essential for organizational success, with DevOps strategies playing a critical role in driving product delivery and maintaining momentum. As organizations transition from legacy to modern infrastructure, many are adopting microservices and cloud-based systems to enhance agility and scalability. The modernization of API frameworks is also crucial, with organizations moving beyond single protocols like REST to support diverse interfaces such as GraphQL and gRPC. API gateways have become key tools for centralizing logic, enhancing security, and reducing redundancies across ecosystems. Automation of API delivery is increasingly important, with practices such as standardizing API specifications, managing source code, using declarative configurations, and leveraging open-source CI/CD tools becoming standard. Kong Konnect platform exemplifies this approach by offering tools like Insomnia for API design and Inso CLI for CI/CD integration, enabling streamlined automation of API delivery and management.

Organizations adopting microservices are increasingly relying on API gateways to enhance the flexibility and scalability of their architectures by addressing the complexities of managing numerous services. An API gateway serves as a single point of entry, providing an abstraction layer that simplifies client interactions by routing requests and aggregating responses, thereby improving performance and reducing latency. It decouples public-facing API endpoints from the microservices themselves, allowing for changes without disrupting client interfaces, which is particularly beneficial during transitions from monolithic to microservice architectures. API gateways enhance security by managing access controls, such as IP whitelists and authentication, and improve load management through features like load balancing and rate limiting, which protect against traffic spikes and potential attacks. With tools like Kong Gateway, organizations can leverage high-availability clusters and a range of plugins to efficiently manage cross-cutting concerns, ensuring a robust, scalable, and secure microservice system.

In a microservices architecture, the decentralized nature of numerous small, independent services necessitates an API gateway to address the resulting complexities and challenges. An API gateway acts as a reverse proxy, providing a single entry point for client applications and managing tasks such as routing requests, aggregating data, and enforcing security measures. This centralization simplifies the development of individual microservices by handling cross-cutting concerns like security, traffic control, and failure management, thereby allowing developers to focus on core business logic. Additionally, API gateways standardize access across microservices, offering protocol translations and a unified domain name to streamline communication and facilitate scalability. The gateway also enhances operational governance by enforcing consistent security, compliance, and performance standards across all services, making it a crucial component for maximizing the potential of microservices architecture. Tools like Kong Gateway exemplify these benefits by providing scalable, secure, and flexible solutions that integrate seamlessly with modern cloud-native infrastructures.

In the context of cloud-native app development, vendor lock-in refers to the challenges organizations face when they become overly dependent on a single cloud service provider, leading to potential issues such as price hikes, service degradation, limited innovation, and single points of failure. To mitigate these risks, companies are encouraged to maintain application portability by avoiding proprietary data formats, using open-source technologies like MySQL, PostgreSQL, MongoDB, and adhering to standards such as OpenAPI for API documentation. Infrastructure alternatives like on-premises, private cloud, multi-cloud, and hybrid cloud architectures offer varying degrees of control, flexibility, and risk management, enabling organizations to select the best options for their specific needs. By leveraging open source tools and modern standards, businesses can avoid becoming overly reliant on a single provider, thus maintaining their ability to innovate and adapt to changing technological landscapes.

APIs and API gateways are susceptible to various security threats if not properly secured, including unauthorized access, injection attacks, and denial of service attacks. To mitigate these risks, it's crucial to implement security measures such as encryption of communications via HTTPS, robust authentication methods, and consistent application of security practices at the API gateway level. API gateways serve as a central point for managing security, enabling rate limiting, request size limiting, and logging to defend against malicious activities while providing an audit trail for API calls. Employing web application firewalls and machine learning can further enhance threat detection and prevention. Additionally, careful design of API endpoints and data exposure, along with regular management of deprecated APIs, helps protect sensitive information and maintain secure operations. By segmenting API gateways for different use cases and applying network access restrictions, organizations can prevent unauthorized access and ensure their APIs are both secure and efficiently managed.

Control plane and data plane are key concepts in both networking and modern infrastructure systems like Kubernetes and service meshes, focusing on the separation of responsibilities within a system. The control plane is responsible for establishing and enforcing policies, managing network layouts, updating routing tables, and controlling traffic flow, while the data plane carries out these established policies, such as routing data packets to their destinations. In Kubernetes, the control plane includes components like the API server and the scheduler, which make global decisions about the cluster, while the data plane is made up of worker nodes and pods that execute these decisions. In service meshes, the control plane manages complex configurations and distributes them to sidecar proxies, which form the data plane, facilitating seamless communication between disparate services. This separation allows for scalable, consistent, and manageable application configurations, reducing the complexity and risk associated with deploying and managing distributed systems.

Cloud-native technology represents an evolving approach in software development that leverages the capabilities of cloud computing platforms, emphasizing modular designs composed of microservices to enhance scalability, agility, and cost-efficiency. By utilizing technologies like containers, service meshes, and declarative APIs, cloud-native applications are designed to be highly available, resilient, and easily scalable across various environments, including public, private, and hybrid clouds. The Cloud Native Computing Foundation (CNCF) promotes these methodologies, providing resources and fostering a community to support the adoption of cloud-native practices. This approach prioritizes application development over infrastructure concerns, enabling businesses to rapidly innovate and respond to user feedback by deploying changes predictably and frequently. By adopting a cloud-native strategy, organizations benefit from reduced total cost of ownership, improved resiliency, and the ability to deliver high-impact changes that drive business value, ultimately gaining a competitive edge in dynamic market environments.

As cloud computing evolves, many businesses are adopting hybrid or multi-cloud models to leverage the best features of different providers, avoid vendor lock-in, and enhance scalability and resilience. The hybrid model involves using both private/on-premise and public clouds, often driven by security concerns or regulatory requirements. In contrast, the multi-cloud model utilizes multiple public clouds to optimize the deployment of distributed applications. Despite their advantages, these models introduce complexities in management and connectivity, prompting the need for effective cross-cloud connectivity solutions. Such solutions streamline administration and ensure seamless interaction between environments, allowing businesses to focus on innovation rather than infrastructure challenges. By using a dedicated connectivity layer, organizations can enhance resilience, achieve better performance, and maintain security while minimizing downtime and operational complexities.

Microservice applications increase the complexity of authentication, authorization, and session management compared to traditional monolithic architecture, necessitating new approaches for these functions. Authentication in microservices is often handled by a dedicated service that ensures users are authenticated and authorized before processing requests, avoiding the redundancy of implementing authentication in each service. Secure token-based authentication is preferred over basic methods to prevent exposing user credentials, with access tokens enabling a time-limited, stateless mechanism for user verification. Session management in distributed microservices can be challenging, as session data must be accessible across multiple servers or containers. Solutions include using a central data store or API gateway to manage session data, ensuring scalability and security. An API gateway can centralize authentication and manage user sessions using tokens like JSON web tokens (JWT) to maintain a stateless architecture while protecting session details from interception. OAuth is recommended for secure third-party application access, and tools like the Kong API gateway offer plugins to streamline authentication and session management across APIs.

Monitoring and distributed tracing are critical for ensuring the observability of production systems, particularly in microservices architectures, by providing real-time insights into system health and performance. Monitoring involves tracking system metrics such as CPU, memory usage, and response times to identify potential issues early, allowing teams to address them before they escalate. It is particularly useful during production tests like canary releases or blue-green deployments to assess their impact. Distributed tracing, on the other hand, focuses on tracking individual operations across microservices, which helps in debugging by piecing together the chain of requests and identifying root causes of failures. Properly implementing distributed tracing involves adding identifiers to requests to enable recreating transaction paths for error investigation. Tools like Kong's API gateway facilitate monitoring and tracing by supporting plugins that integrate with services like Zipkin for distributed tracing. Together, these practices enable rapid issue identification and resolution, allowing for quick deployment of fixes and continuous improvement in system robustness, which supports ongoing innovation and adaptation to user needs.

RESTful API design, rooted in the architectural pattern introduced by Roy Fielding in 2000, emphasizes creating APIs that are easy to use and implement by adhering to six key architectural constraints. The approach prioritizes the use of native HTTP methods, descriptive endpoints, and readable responses, often utilizing JSON for its lightweight syntax. While RESTful principles offer a foundation for building intuitive APIs, their success also hinges on comprehensive documentation and version management using practices like Semantic Versioning. Security considerations are crucial, with emphasis on encrypting traffic, using secure authentication methods, and crafting error messages that are informative yet protective of sensitive information. By focusing on thoughtful design over specific implementation details, developers can create APIs that are more likely to be widely adopted and effectively integrated into client applications.

An API Gateway serves as a crucial component in modern application architecture by acting as a reverse proxy that routes requests to backend services while offering additional features such as security, monitoring, and rate limiting. API Gateway policies centralize governance for APIs by allowing cross-cutting concerns to be configured at the gateway level, which enforces consistent standards across all proxied APIs. This centralized approach contrasts with API policies that attach to individual APIs, as gateway policies apply blanket rules, like authentication and rate limiting, ensuring uniform security and operational practices. Implementing gateway policies streamlines API management by reducing duplicate logic, enhancing governance, and accelerating API delivery through reusable, modular configurations. By applying gateway policies, organizations can maintain consistent security and operational protocols, making APIs easier to manage and develop while ensuring compliance and reliability. These policies are managed like software products, emphasizing modular design, thorough testing, and lifecycle management, ultimately forming the foundation for a seamless, governed API ecosystem.

An API gateway's role as a single access point for an application's APIs does not necessitate it being a single point of failure, which is where a high availability (HA) cluster becomes essential. HA clusters consist of multiple gateway nodes across different servers or locations, ensuring that if one node fails, others can continue to route requests and maintain service uptime. This setup is crucial for enterprises where downtime in online services, such as e-commerce or banking, can have significant financial and reputational impacts. The use of load balancers helps distribute traffic across nodes, and the addition of a distributed data store aids in maintaining configuration consistency and resilience to hardware failures. Specifically, the Kong API Gateway simplifies the implementation of HA clusters by allowing nodes to share a common data store, thus avoiding the need for configuration replication, and uses a local cache system to enhance performance and maintain eventual consistency. This architecture ensures that applications can effectively handle high traffic volumes and unexpected spikes while remaining operational despite potential hardware failures.

APIs are crucial for modern digital communication, necessitating robust API gateways to manage traffic, ensure security, and provide operational metrics. As API gateways become targets for increasingly sophisticated cyber threats, organizations must implement comprehensive security architectures, including authentication, authorization, and threat prevention measures, to protect against attacks like DDoS and SQL injection. Traditional static security controls are insufficient for today's complex environments, where APIs can span multiple regions and organizations. Best practices for securing APIs include using HTTPS, rotating SSL certificates, implementing rate limiting, and employing modern security protocols such as OAuth 2.0 and mTLS. Additionally, monitoring tools like SIEM and SOAR can enhance visibility and automate threat response, while the zero-trust model and service meshes like Kuma provide granular security at the service level. Together, these strategies and technologies form a multi-layered defense for safeguarding API-centric architectures against evolving threats, ensuring the reliability and integrity of interconnected services.

Microservices orchestration tools are essential for managing the complexity of applications built on microservices architectures, which are often spread across multiple containers. These tools automate the coordination, configuration, and operationalization of containers, akin to conducting an orchestra to create harmonious interactions between services. Container technology, as the next step in the evolution from virtual machines, provides faster deployment and testing with better isolation, making it suitable for microservices. Orchestration tools, such as Kubernetes, Azure Kubernetes Service, Apache Mesos, Amazon ECS, and Netflix's Conductor, are popular for their ability to streamline container management, offering features like workload scaling, service discovery, and high availability. They are instrumental in supporting Continuous Integration and Continuous Delivery workflows, allowing developers to efficiently scale applications while maintaining functionality and productivity.

Kong has introduced significant enhancements to its DB-less mode by integrating the Lightning Memory-Mapped Database (LMDB) as its new storage engine, addressing scalability challenges faced by the previous shdict-based system. LMDB's advantages include its small footprint, native support for multi-process operations, and full ACID transaction capabilities, which improve memory usage, scalability, and performance in Kong's proxy operations. This upgrade allows for better handling of large configurations, reduces the complexity of maintaining config storages, and enhances the efficiency of the hybrid mode deployments. Performance benchmarks demonstrated substantial reductions in config loading latency and router rebuild times, as well as increased request per second (RPS) rates during background config updates. Kong has released a technical preview of this new implementation and plans to continue refining LMDB integration, encouraging feedback from users to inform future developments.

Kubernetes, often abbreviated as K8s, is an open-source platform designed for automating the deployment, scaling, and management of containerized applications across distributed systems. It operates within a cluster architecture consisting of worker nodes and a control plane. The control plane, acting as the system's brain, manages container deployments to worker nodes using components such as the kube-apiserver, kube-controller-manager, kube-scheduler, and etcd. Worker nodes, which can run on Linux or Windows, execute containerized applications organized into pods, with core components including kubelet, kube-proxy, and a container runtime. Kubernetes supports high availability and flexibility, making it suitable for deploying microservices and implementing DevOps practices. It can be deployed across various environments, including public clouds, private clouds, and on-premise setups, with the ability to run on a single machine for development and testing purposes.

Service discovery is a crucial element in microservices architectures, facilitating seamless communication and decoupling between services by automating the detection and identification of service instances within a networked environment. This process abstracts the actual locations of service instances, enabling dynamic interaction without static network locations, which optimizes adaptability and resource utilization. By maintaining a real-time registry of service instances, service discovery ensures uninterrupted service communication, enhancing system reliability and performance. It employs client-side or server-side patterns to manage service instance retrieval and load balancing, and leverages protocols like DNS and HTTP-based APIs for efficient service interactions. Popular tools and frameworks such as Consul, Eureka, Etcd, and Kubernetes offer robust capabilities for implementing service discovery, allowing developers to focus on scaling and refining applications as microservices ecosystems expand. By integrating service discovery with frameworks like Spring Cloud, development teams can streamline service registration, discovery, and load balancing, promoting agile and responsive service architectures.

As organizations increasingly adopt microservices architectures, adapting testing strategies becomes crucial to fully leverage the benefits of loosely coupled systems. This shift aligns with agile development practices and DevOps cultures, emphasizing responsiveness, quality, and availability. Microservices, characterized by multiple independently developed services, allow faster development cycles and flexible updates, supported by containerized, cloud-hosted infrastructures. Traditional monolithic testing strategies are inadequate for microservices, necessitating a comprehensive approach that includes automated unit, service, integration, and component tests, along with contract, end-to-end, and UI tests. Automation is key to efficiency, enabling frequent and consistent testing, and is integral to a continuous integration and deployment pipeline. The Testing Pyramid advises a balance, with most tests as unit tests, followed by fewer system and UI tests due to cost and complexity. Post-production testing, chaos engineering, monitoring, distributed tracing, and deployment strategies like canary releases and blue-green deployments further ensure system resilience and performance. Manual testing, including exploratory and user acceptance testing, remains valuable, offering unique insights that feed back into automated processes. This multifaceted approach supports independent microservices deployment, facilitating incremental changes and frequent releases, ultimately enhancing user satisfaction and system quality.

Microservices architecture allows for the division of applications into task-specific services that can be independently programmed, maintained, and upgraded, enhancing the agility and efficiency of development teams while reducing the risks associated with traditional monolithic structures. This architecture supports parallel development by enabling teams to work on different components simultaneously, improving error detection and minimizing downtime during updates. An API gateway acts as a client-facing front for microservices, managing requests and providing additional functionalities such as authentication, load balancing, and monitoring, thus simplifying the complexity of service interactions. Kong Gateway, an example of such a gateway, offers a platform-agnostic, open-source solution that can grow with applications, supporting both monolithic and microservice architectures, and is compatible with hybrid platforms, including Kubernetes.

Service-Oriented Architecture (SOA) is a strategic design framework that organizes software applications into a collection of loosely coupled services, enabling seamless integration and communication over a network. This approach enhances system agility by breaking down monolithic applications into modular, reusable components, thereby promoting efficiency and reducing redundancy. SOA is widely adopted across various industries, such as e-commerce, finance, and healthcare, to streamline operations and improve customer experience. It facilitates better interoperability and flexibility, allowing organizations to respond swiftly to changing business requirements. Key principles of SOA include interoperability, loose coupling, and abstraction, which foster collaboration and innovation while maintaining system scalability and adaptability. Challenges such as complexity, performance overhead, and governance must be managed to leverage SOA's full benefits. The advent of microservices architecture represents an evolution of SOA principles, emphasizing decentralized management and lightweight, independently deployable services to align with modern software delivery practices.

The rapid evolution of API management has led to significant changes in deployment patterns, with a growing demand for flexible and adaptable solutions that can operate across various infrastructures, including cloud, on-premises, and hybrid environments. Traditional API management platforms like Apigee, which were initially deployed as SaaS monoliths in the cloud, are now being challenged by the likes of Kong, which offers more deployment flexibility and cloud-agnostic capabilities. Kong supports a wide range of infrastructures, from bare metal to Kubernetes, allowing for seamless integration with native services on any public cloud without sacrificing functionality or performance. It provides a unified API gateway runtime that supports various deployment patterns such as microgateways, hybrid setups, and Kubernetes ingress, enabling organizations to maintain a consistent configuration across different environments. Additionally, Kong's open-source nature and extensive plugin ecosystem allow for easy customization and extension of its functionality, making it a versatile choice for modern API management needs.

A recent conversation with a major Swedish bank has sparked a deep reflection on the role of technology, particularly APIs, in combating climate change. The text emphasizes the urgent need for technologists, vendors, suppliers, engineers, and architects to accept their responsibility in reducing resource consumption and carbon emissions. It highlights that while digital transformation often celebrates innovation, it is largely driven by energy from fossil fuels, which exacerbates environmental issues. APIs, which account for a significant portion of global web traffic, are identified as a critical area where efficiency improvements can lead to substantial energy savings and cost reductions. The text advocates for designing, building, and managing APIs with sustainability in mind by minimizing unnecessary data processing and optimizing deployment strategies. It stresses that consumers are increasingly prioritizing sustainability, with many willing to pay more for environmentally friendly products, thus putting pressure on companies to prove their sustainability credentials. The article is part of a series that will further explore how APIs can support sustainability goals and the implications of architecture choices on environmental impact.

Organizations deploying Kong Mesh in environments with multiple security domains must consider various architectural approaches to meet specific security requirements. Kong Mesh, built on the CNCF-hosted Kuma project, offers three main strategies: using a zone, a mesh, or the global control plane as the security domain boundary. Each approach has distinct advantages and disadvantages, such as enhanced flexibility with zones, the logical separation of policies with meshes, or complete independence with the global control plane. Zones allow for flexible application of mesh policies but risk unintentional cross-domain traffic without proper policies. Meshes provide separate policy domains, reducing the chance of misapplied policies, while supporting cross-mesh inspection and controls. The global control plane approach offers complete autonomy for each security domain but requires separate policy management, which could increase operational overhead. Ultimately, the choice depends on the organization's specific needs, whether they require strict isolation or flexible integration, as Kong Mesh supports diverse configurations to accommodate different security requirements.

Kong has released version 2.8 of its Gateway, enhancing API management and security features across infrastructures. Key updates include a beta version of secrets management, which centralizes sensitive information to improve security and compliance by integrating with tools like AWS Secrets Manager and HashiCorp Vault. This feature allows operators and developers to work separately while maintaining secure API operations. The release also introduces improvements to Kong Manager, such as new filtering and sorting capabilities that streamline API management. Additionally, the Forward Proxy Advanced plugin now supports Mutual Transport Layer Security (mTLS), enhancing security for connections involving HTTP proxies. The update also includes enhancements to various plugins and the decK tool, which now supports default values and online validation for configurations. Both the commercial and open-source versions of Kong Gateway 2.8 are available for download, and users are encouraged to upgrade and explore the new features.