Transforming the Omni-Channel Experience at Kroger
summary
Kroger refactors an on‑prem stack into a cloud‑native, hybrid platform on Kubernetes, building hundreds of microservices and componentized UIs, using open source and commercial open source. Data tier choices include Elasticsearch, Redis, Cosmos and YugabyteDB (YSQL/YCQL) for multi‑API compatibility, geo‑distributed or cross‑region async replication, and active‑active topologies. Teams spend six to nine months testing, achieve single‑digit millisecond data latencies, and use async replication and planned CDC to power shopping lists and checkout.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:18About Kroger
- 1:53Why are you doing this
- 3:59What are you doing
- 7:06Technology stack
- 7:43Why gigabyte
- 9:45Deployment topologies
- 12:28Additional product offerings
related talks
36mFireside Chat with Kroger: Examining their Two-Year Distributed SQL Journey & What's Next
24mMastering API Consistency: Kroger's Journey and Tools
50mBuilding And Deploying Omni-Channel Digital Experiences At Scale
19mKeynote: From COBOL to Kubernetes: A 250 Year Old Bank's Cloud-Native Journey
19mBuilding a resilient system with Frappe and Kubernetes
37mDelivering agility at McDonald's with microservices transformation
09mThe cloud native elephant in the room
28mFlexible Cloud, Whatever The Workload