How Target is enhancing retail discovery and cutting database maintenance by 50% with Spanner Graph
In today's retail environment, shoppers expect highly personalized product discovery experiences and conversational assistance that feels genuine, natural, and genuinely helpful. Today, successful product discovery is about understanding semantic meaning and the rich, connected relationships between products, categories, and guest intent. It is no longer just about keywords and basic browsing.
Key Takeaways
- At Target, this work is handled by our Guest Product Confidence platform team.
They are responsible for building the features that establish trust and guide purchasing decisions, such as ratings, reviews, and AI-driven digital shopping assistants.
- In this post, we'll explore how we achieved all four with Spanner.
Overcoming fragmented architecture Previously, Target's discovery data ecosystem relied on a combination of Elasticsearch clusters for search and inverted indexes, alongside separate NoSQL datastores for our transactional data.
- High operational overhead: Managing independent clusters, tuning search indexes, and handling complex, custom synchronization and aggregation logic required intensive manual intervention from our engineering teams.
Expansion bottlenecks: Expanding our retail data domains required adding new database collections, maintaining complex joins, and navigating weak transactional guarantees across our discovery and core transactional systems.
- However, adding more single-purpose databases would have only worsened our operational complexity and data synchronization pipelines.
We ultimately chose Spanner Graph to build our enterprise ontology, which is a "graph-of-graphs" paradigm that allows us to construct a massive, generative AI-powered shopping graph.
- Unified graph, vector, and search store Instead of shifting data across multiple databases, Spanner Graph stores our entity nodes, relationship edges, and vector embeddings in the same database engine.
At Target, this work is handled by our Guest Product Confidence platform team. They are responsible for building the features that establish trust and guide purchasing decisions, such as ratings, reviews, and AI-driven digital shopping assistants. An exciting example of this is our Gift Finder chat agent , which we launched during the 2025 holiday season online and in the Target app to help shoppers discover the perfect items through friendly, conversational dialogue.
To deliver real-time personalization and context-rich semantic responses like these at global scale, we identified a critical architectural need to move away from a fragmented data ecosystem toward a unified data platform. We needed a solution capable of supporting high-throughput transactional workloads, highly connected graph relationships, vector similarity search, and full-text keyword search all at once. In this post, we'll explore how we achieved all four with Spanner.
Overcoming fragmented architecture Previously, Target's discovery data ecosystem relied on a combination of Elasticsearch clusters for search and inverted indexes, alongside separate NoSQL datastores for our transactional data. While functional, this fragmented architecture presented significant operational and technical challenges. Disconnected context: Keeping separate search, vector, and transactional databases in perfect sync was a constant challenge.
Siloed information led to missing context, disconnected attribute relationships, and inconsistent query results. High operational overhead: Managing independent clusters, tuning search indexes, and handling complex, custom synchronization and aggregation logic required intensive manual intervention from our engineering teams. Expansion bottlenecks: Expanding our retail data domains required adding new database collections, maintaining complex joins, and navigating weak transactional guarantees across our discovery and core transactional systems.
Siloed intelligence: We lacked the ability to query graph relationships, vector similarity, and keyword search indexes in a single transaction. To build the next generation of AI-driven guest experiences, we needed to consolidate on one platform. Building the enterprise ontology on Spanner Graph We evaluated multiple specialized technologies, including standalone vector databases and niche graph databases.
However, adding more single-purpose databases would have only worsened our operational complexity and data synchronization pipelines. We ultimately chose Spanner Graph to build our enterprise ontology, which is a "graph-of-graphs" paradigm that allows us to construct a massive, generative AI-powered shopping graph. By unifying our data, we bring semantic data, graph relationships, vector embeddings, and operational transactions under one roof.
This establishes Spanner as our single authoritative source of truth for both transactional state and semantic intelligence. Our high-level architecture now consists of three core pillars: 1. Enterprise augmentation This layer captures our enterprise retail catalog, aggregates relevant metadata from multiple backend sources, and utilizes generative AI for agentic data enrichment to dramatically improve the quality and depth of the product data we ingest.
For more details please read the original article at Google Cloud AI.
Continue Learning
Comments
Sign in to join the conversation