Sprint 3 project, view 1: the request and data path

Scroll or pinch to zoom, drag to move, double-click to zoom in 100% SVG PNG Back to the post

View 1, request and data path: the customer resolves the shop name through Cloud DNS and k8gb, reaches Cloud Load Balancing and Higress, which validates a Keycloak token and routes to the order service; the order service calls the Dubbo pricing service over Triple, publishes an event through Dapr to Kafka, whose schema is checked by Apicurio Registry; the inventory service consumes the event and reserves stock in TiKV; TiKV and Kafka use OpenEBS volumes; Kuma secures the sidecars with mutual TLS.