api7 / api7/ngx_http_ffi_client
Slice 5: integration and cutover
Open
Nobody has claimed this yet.
area:ai
enhancement
scenario-intake
- Dominant language
- C
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Part of the lua-resty-http parity effort. Design / rationale: RFC api7/rfcs#115.
Scope
Wire the client into ai-proxy and cut over.
- Behind a flag in
ai-transport/http.luaand the provider drivers. - Run the API7 EE AI demo and
ai-proxy-multi; benchmark against lua-resty-http; then flip the default. - Land the transport change in EE and APISIX together, word-for-word identical.
Acceptance
- Demo +
ai-proxy-multipass on the FFI client. - Benchmark shows the expected outbound CPU reduction.
- EE and APISIX transport diffs are identical.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ai-transport/http.lua and the provider drivers, then review RFC api7/rfcs#115 and the existing API7 EE AI demo and ai-proxy-multi paths. Run the demo and ai-proxy-multi with the FFI client, benchmark against lua-resty-http, and verify the EE and APISIX transport diffs are word-for-word identical before changing the default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua
- Domain
- api, backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100