Don't Panic — Kong Gateway

Kong Gateway is a reverse proxy with a plugin hobby. Clients hit Kong. Kong matches a Route, runs whatever plugins you attached, and forwards the request to a Service (optionally through an Upstream and its Targets). That entity graph is the whole plot. Everything else is scenery.

Before gateways like this, every microservice quietly reinvented authentication headers, rate limits, and logging formats, then disagreed about all three in production. Kong exists so those shared worries live at the edge once, while backends keep their domain logic.

Three ideas hold the rest of the course:

1. Proxy path versus control path. Port 8000 (typical) is for clients. Port 8001 (typical) is the Admin API, which can rewrite your entire routing and credential universe. Confusing them is how friendly demos become incident tickets.

2. Configuration is data. You can poke the Admin API one object at a time, or load a declarative YAML that replaces the graph in one shot. DB-less mode keeps that graph in memory and answers entity writes with HTTP 405. Hybrid mode parks the database on control plane nodes and pushes config to data planes that keep serving from cache if the control plane naps.

3. Plugins are interest on the hot path. Official sizing guidance is blunt: more Routes and plugins mean more latency per request. Entity count is a capacity metric, not interior decoration.

The surprise for many first-time operators: the Admin API is not a metrics scrape port with opinions. Bind it to the world without controls and you have handed out cluster keys. The Field Notes tab is where that judgment lives; the Cheatsheet tab is where the port table and topology matrix live when you need them at 2 a.m.

What to open next:

• Intro if you want the full architecture and glossary in one sitting.
• Practice / Exercise if you learn by curling a DB-less container until a 429 appears.
• Landscape if you are still choosing among managed cloud gateways, plain NGINX, Envoy, or Konnect.
• Timeline if you care how declarative config, hybrid mode, and Konnect arrived in that order.

You do not need to memorize every plugin. You need the request path, the control path, and the habit of treating config releases like application releases. The rest of Kong is plugins and patience.