How fangfengxiang/kong-plugin-yar-grpc works
This Kong plugin exposes two access-phase protocol-bridge directions: gRPC requests can reach PHP Yar services, and PHP Yar requests can reach gRPC services. The README documents the plugin’s handler and schema, plus the bridge package’s endpoint, orchestration, and transport layers; those bridge internals are external dependencies, not files in this repository. Relationships below are documented in the README; no source excerpts were available.
Main entry points: handler.lua Access handler
Components 12
Kong plugin
- Access handler
kong/plugins/yar_grpc_bridge/handler.lua - Config schema
kong/plugins/yar_grpc_bridge/schema.lua
Bridge runtime
- gRPC-to-Yar entry
- gRPC-to-Yar orchestration
- Lua Yar client
- Yar-to-gRPC entry
- Yar-to-gRPC dispatch
- gRPC transport
Backend services
- PHP Yar server
- Go gRPC server
Other components
- gRPC client
- PHP Yar client
Connections 10
- gRPC client → Access handler: sends HTTP/2
README.md - Access handler → gRPC-to-Yar entry: dispatches grpc2yar
README.md - gRPC-to-Yar entry → gRPC-to-Yar orchestration: calls
README.md - gRPC-to-Yar orchestration → Lua Yar client: uses
README.md - Lua Yar client → PHP Yar server: calls
README.md - PHP Yar client → Access handler: sends HTTP/1.1
README.md - Access handler → Yar-to-gRPC entry: dispatches yar2grpc
README.md - Yar-to-gRPC entry → Yar-to-gRPC dispatch: calls
README.md - Yar-to-gRPC dispatch → gRPC transport: uses
README.md - gRPC transport → Go gRPC server: calls
README.md