Wave Retail Demo Orchestrator
Single landing page for the demo platform: where to go, what each component does, and how indexing/search/recommendations flow through the system.
Demo-only topology
AKS wave-dev
Kaniko in-cluster builds
STS + scoped JWTs
Platform overview
- wave-sts issues audience-scoped tokens and enforces scope contracts.
- wavestore-erp-api is source-of-truth for products, stock, pricing, orders, and catalog export.
- wavesearch-api ingests ERP catalog snapshots, rebuilds runtime index, serves search/recommend APIs, and tracks events/analytics.
- Frontends: storefront (shopper), ERP admin, and WaveSearch Labs operator UI.
- Ingress: all hosts route through one shared nginx ingress public IP.
Shopper experience
Bootswatch storefront for demo shopping, recommendations, and order placement.
ERP admin
WaveFunction-style admin UI for catalog, stock, pricing, customers, orders, and invoices.
Search Labs + platform docs
WaveFunction-style control UI for ingestion, merchandising, analytics, plus platform guide.
Original storefront (preserved)
Legacy WaveStore/Pico Outfitters storefront from the earlier demo build, kept live for reference and comparison.
How data flows
- Storefront basket/checkout calls
/v2/checkout, which places authoritative orders in ERP.
- ERP updates product/stock/pricing state.
- Labs calls
/search/ingest/from-erp to pull ERP catalog export.
- WaveSearch rebuilds runtime index and serves query/recommend endpoints.
- Storefront consumes those APIs and posts events back for analytics.