How I Stopped Coding Repetitive Service Components with Kong

• Kong

  18 37,748 9.9 Lua

  🦍 The Cloud-Native API Gateway and AI Gateway.

  

The Kong Gateway product allows the complexity of my service-tier APIs to be reduced to a collection of end points (or URIs) focused on meeting a collection of business needs and functionality. Often duplicated components (like authentication, logging, and security) are handled by the gateway and can be removed from the service-tier design. In addition to the common components shown in the original illustration, Kong Gateway offers additional functionality:

• kuma

  5 3,536 9.9 Go

  🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project.

  

Taking things to a broader level, Kuma is another platform agnostic-OSS solution for service mesh and microservice management – with control plane support of Kubernetes, virtual machines (VM), and even bare-metal environments. Kuma was donated to the Cloud Native Computing Foundation (CNCF) by Kong and still actively contributes to the evolving code base.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• kubernetes-ingress-controller

  8 2,142 9.9 Go

  :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.

  

For those organizations using Kubernetes for their container orchestration, Kong created the Kong Ingress Controller which implements authentication, transformations, and other functionalities (via plugins) across Kubernetes clusters. Kong Ingress Controller updates a standard Kubernetes implementation as shown below:

Suggest a related project