Kong Course
API gateway patterns you learn by sending requests through it, not by reading about it.
Take this course in the learning hubLessons
- Why put a gateway in front?Ten services each solving auth, rate limits and logging their own way is the problem Kong fixes.
- Services and RoutesKong's whole data model in two objects - and you learn it by sending requests at it.
- When two routes both matchThe rule that decides the winner, and the mistake that makes a route unreachable.
- Plugins: behaviour without codeWhat a plugin is, where you attach it, and why scope is the thing people get wrong.
- The request lifecycleThe phases a request passes through, and why the order explains most surprises.
- Consumers and API keysWho is calling matters - here you can watch a request pass and fail on the key alone.
- Rate limiting you can trip yourselfPress Send six times and watch the sixth one fail - that is the lesson.
- Choosing an auth pluginFour options, and a decision tree that gets you to the right one in three clicks.
- Upstreams, targets and healthHow Kong spreads traffic and takes a sick instance out of rotation.
- DB-less or database mode?A genuine architectural fork - and the one that decides how you deploy.
- Declarative config and decKTreat gateway config the way you treat code: in git, diffed, reviewed, applied.
- Seeing what the gateway seesThe gateway is the one place that sees every request - use it.
- Kong on KubernetesThe Ingress Controller turns Kubernetes resources into Kong config for you.
- Before you put it in front of productionThe gateway becomes the thing everything depends on - here is what that demands.
- Where a gateway spends its timeEvery plugin is on the critical path of every matching request.