Sofia added ETag support and defended the per-request hash by leaning on the existing cache to absorb cost.
task
ticketacme/api#88submitted by@sofiacreated19d ago
plansigned
Add ETag support to /products so the frontend can short-circuit unchanged responses.
Compute the ETag from a hash of the response body.
findings2
performancedefendedf_1
Hashing the full body on every request is expensive at peak
At peak the catalog response is ~200KB. Hashing per-request adds CPU. Consider hashing the upstream version-token instead.
Catalog DB doesn't expose a version-token yet; opened a follow-up ticket. For now hashing is bounded by the existing cache layer so most requests skip it.
decided —
conventionaddressedf_2
Observability registration present
ETag hit ratio is reported via @acme/observability.