How nojorono/core-gateaway works
This repository documents a Kong API Gateway in front of four backend domains: WMS, Marketing Dashboard, Retailer Yield Optimization, and Master Data. The principal workflow is a client request entering Kong and being routed to a backend service; authentication is described as an optional plugin capability. The README notes that backend images are illustrative httpbin examples. Source excerpts were unavailable, so backend internals and specific route-to-service mappings are not inferred.
Main entry points: kong.yml Kong Gateway · backend-wms Warehouse Management · backend-md Marketing Dashboard · backend-ryo Retailer Yield Optimization
Components 7
API Gateway
- Kong Gateway
kong.yml
Backend Services
- Warehouse Management
backend-wms - Marketing Dashboard
backend-md - Retailer Yield Optimization
backend-ryo - Master Data Service
service-meta
Other components
- API Client
- JWT Plugin
Connections 6
- API Client → Kong Gateway: sends requests
- Kong Gateway → Warehouse Management: routes requests
- Kong Gateway → Marketing Dashboard: routes requests
- Kong Gateway → Retailer Yield Optimization: routes requests
- Kong Gateway → Master Data Service: routes requests
- Kong Gateway → JWT Plugin: may invoke