16Follow one log line from the application into Elasticsearch and onto the Kibana screen. Where does this path break at scale?▼mediumAmazon & AWSFlipkartJPMorgan ChaseunlockedThe data-path question separates people who have sized a cluster from people who installed one. Shard sizing, refresh versus flush, and each ILM phase carry one specific failure mode apiece.Open full answer →
21Design type-ahead search for a marketplace with fifty million products. It must feel instant.▼mediumGoogleLinkedInAmazon & AWS○ sign inType-ahead is a latency budget wearing a search costume: keystrokes arrive every 200 milliseconds, so anything slower feels broken. Prefix indexes, freshness tiers, and typo tolerance are the scored parts.Open full answer →
27Search results lag the database by minutes and it costs money. Design the sync, and plan for the day you must rebuild the whole index.▼hardLinkedInFlipkartWalmart Global Tech○ sign inDual-writing from application code is the answer that fails quietly six months in. Change data capture, per-entity ordering, and a reindex you could run on a Tuesday are what interviewers score.Open full answer →
