Architecture comparison

Lowe\u2019s vs Walmart

Lowe\u2019s runs closer to the foundational model (Native (own / self-hosted weights)) than Walmart (Off the LLM map (in-house non-LLM ML)). No shared foundational model — different bets.

Lowe\u2019s

Retail

Proximity

Native (own / self-hosted weights)

Models

Google · Geminiproprietary / self-built models

Cloud · datastore

GCPown

Compliance

SOC 2PCI DSS

Architecture

Home-improvement retailer on Google Cloud; Gemini-based associate/customer assistants + own ML.

Walmart

Retail

Proximity

Off the LLM map (in-house non-LLM ML)

Models

—

Cloud · datastore

HybridApache KafkaSpark StreamingStormHDFSNoSQL databasesCassandra

Compliance

TLS/HTTPSenterprise network segmentationmulti-cloud container orchestration controlsconfiguration management/drift control

Architecture

Walmart’s production architecture is hybrid and multi-cloud: public-cloud workloads run across Azure and Google Cloud, while core infrastructure and brokers remain within Walmart-controlled private cloud environments.[1][2][7][10][15] The platform is heavily event-driven and containerized, with Kafka as a central backbone and WCNP/Kubernetes used for consumer workloads across clouds.[1][4]

← Full orbit map · Score your own stack →