higress-group/higress

Support APISIX plugin - proxy-cache

Open

#679 opened on Dec 10, 2023

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Go (1,219 forks)github user discovery
area/plugingood first issuehelp wantedlevel/normalsig/wasm

Repository metrics

Stars
 (9,036 stars)
PR merge metrics
 (Avg merge 7d 9h) (18 merged PRs in 30d)

Description

https://apisix.apache.org/docs/apisix/plugins/proxy-cache/

In implementation, however, we need not replicate APISIX exactly, but instead should focus on the actual user needs behind the plugins, combined with the specific circumstances of Higress, to re-abstract configuration fields and corresponding capabilities. We can draw lessons from others, but we should not copy them exactly.

Contributor guide

Research direction
Analyze the APISIX proxy cache plugin documentation and code to understand its caching behavior and configuration fields. Then study Higress's existing caching infrastructure (if any) and propose a simplified abstraction that meets user needs without direct replication. Focus on key features like cache key, storage backend, TTL, and cache bypass rules.
Tech stack
go
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoAPI Gateway
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55