Stop caching reads on a read-write API

The proxy cache held every GET on the whole service for 60 seconds, and these
APIs accept writes. Kong's proxy cache has no invalidation on write: a POST
that changes a product passes through the same gateway, and the gateway goes on
serving the value it captured before it, for up to a minute, with nothing in the
response saying so.

It produced a real wrong answer. An agent woken by a stock event read the figure
from before that event and reported, in one sentence, "68 in stock, above the
threshold" and "it crossed the threshold, from 68".

The manifest is kept, unreferenced, carrying the reason — so reinstating it is a
decision rather than a rediscovery.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

This commit is contained in:

Stéphane Tailland

2026-08-31 08:26:25 +02:00

parent e9997c360e

commit 613de34bd2

3 changed files with 18 additions and 19 deletions

									
										kong/kustomization.yaml
									
		-1
	
												View File
												
				@@ -7,7 +7,6 @@ resources:

				  - rest/path-rewrite-bindings.yaml

				  - rest/kongplugin.yaml

				  - rest/rate-limiting.yaml

				  - rest/proxy-cache.yaml

				  - rest/audit-log.yaml

				  - rest/audit-log-body-capture.yaml

				  - rest/audit-log-body-capture-bindings.yaml