How vedant9912/search-as-you-type-autocomplete-engine works
This Spring Boot backend supports three search paths: a MySQL prefix-search baseline, in-memory Trie prefix results, and popularity-ranked Top-K results. Startup seeds an empty database, loads products once to build the Trie and popularity map, and publishes them through a holder; live Trie searches avoid database access. The API also exposes latency benchmarks for each search approach. Relationships below follow the README or the excerpted caller code; no unsampled implementation links are assumed.
Main entry points: SearchController.java Search controller · Trie.java Prefix Trie · DataInitializer.java Data initializer · ProductRepository.java Product repository
Components 12
API and benchmarks
- Spring Boot app
src/main/java/com/autocomplete/autocompleteengine/AutocompleteEngineApplication.java - Search controller
src/main/java/com/autocomplete/autocompleteengine/controller/SearchController.java - Latency statistics
src/main/java/com/autocomplete/autocompleteengine/util/LatencyStats.java
Startup and state
- Data initializer
src/main/java/com/autocomplete/autocompleteengine/config/DataInitializer.java - Trie holder
src/main/java/com/autocomplete/autocompleteengine/config/TrieHolder.java
Search and ranking
- Prefix Trie
src/main/java/com/autocomplete/autocompleteengine/trie/Trie.java - Trie node
src/main/java/com/autocomplete/autocompleteengine/trie/TrieNode.java - Popularity map
src/main/java/com/autocomplete/autocompleteengine/config/DataInitializer.java
Product catalog
- Product repository
src/main/java/com/autocomplete/autocompleteengine/repository/ProductRepository.java - Product entity
src/main/java/com/autocomplete/autocompleteengine/model/Product.java - MySQL database
Other components
- Client
Connections 17
- Client → Search controller: sends requests
src/main/java/com/autocomplete/autocompleteengine/controller/SearchController.java - Spring Boot app → Search controller: serves API
src/main/java/com/autocomplete/autocompleteengine/AutocompleteEngineApplication.java - Search controller → Product repository: queries baseline
src/main/java/com/autocomplete/autocompleteengine/controller/SearchController.java - Search controller → Trie holder: reads shared state
src/main/java/com/autocomplete/autocompleteengine/controller/SearchController.java - Search controller → Prefix Trie: runs prefix search
src/main/java/com/autocomplete/autocompleteengine/controller/SearchController.java - Search controller → Prefix Trie: runs Top-K
src/main/java/com/autocomplete/autocompleteengine/controller/SearchController.java - Search controller → Latency statistics: calculates percentiles
src/main/java/com/autocomplete/autocompleteengine/controller/SearchController.java - Data initializer → Product repository: seeds and loads
src/main/java/com/autocomplete/autocompleteengine/config/DataInitializer.java - Data initializer → Prefix Trie: inserts product names
src/main/java/com/autocomplete/autocompleteengine/config/DataInitializer.java - Data initializer → Trie holder: publishes state
src/main/java/com/autocomplete/autocompleteengine/config/DataInitializer.java - Data initializer → Popularity map: builds popularity data
src/main/java/com/autocomplete/autocompleteengine/config/DataInitializer.java - Trie holder → Prefix Trie: holds instance
src/main/java/com/autocomplete/autocompleteengine/config/TrieHolder.java - Prefix Trie → Trie node: traverses nodes
src/main/java/com/autocomplete/autocompleteengine/trie/Trie.java - Product repository → MySQL database: queries and saves
src/main/java/com/autocomplete/autocompleteengine/repository/ProductRepository.java - Product repository → Product entity: returns products
src/main/java/com/autocomplete/autocompleteengine/repository/ProductRepository.java - Product entity → MySQL database: maps catalog rows
src/main/java/com/autocomplete/autocompleteengine/model/Product.java - Search controller → Popularity map: ranks using
src/main/java/com/autocomplete/autocompleteengine/controller/SearchController.java