How sbezhuk/beebase-gateway works
BeeBase Gateway is a stateless HTTP reverse proxy: clients send requests to one entry point, which routes each request to the backend service that owns that API path. The gateway also answers its own health and readiness checks and forwards paths, queries, and authorization headers without business logic or token verification. Configuration supplies each upstream URL. Routing details are documented in the README and sampled router source; backend services are external to this repository.
Main entry points: proxy.go Reverse proxy · main.go Gateway process · router.go HTTP router · config.go Runtime configuration
Components 14
Gateway entry
- Gateway process
cmd/gateway/main.go - Runtime configuration
internal/config/config.go
Routing and proxy
- HTTP router
internal/transport/http/router.go - Reverse proxy
internal/proxy/proxy.go
Other components
- HTTP client
- Auth service
- Apiary service
- Hive service
- Inspection service
- Harvest service
- Media service
- Statistics service
- Subscription service
- Notification service
Connections 15
- HTTP client → Gateway process: sends request
- Gateway process → Runtime configuration: loads settings
- Gateway process → Reverse proxy: builds proxies
- Gateway process → HTTP router: installs handler
- Gateway process → HTTP client: serves response
- HTTP router → Reverse proxy: dispatches request
- Reverse proxy → Auth service: forwards request
- Reverse proxy → Apiary service: forwards request
- Reverse proxy → Hive service: forwards request
- Reverse proxy → Inspection service: forwards request
- Reverse proxy → Harvest service: forwards request
- Reverse proxy → Media service: forwards request
- Reverse proxy → Statistics service: forwards request
- Reverse proxy → Subscription service: forwards request
- Reverse proxy → Notification service: forwards request