Loading…
While this loads — quick one
Every subscriber must get each event. A queue, or pub/sub?
Loading…
While this loads — quick one
Every subscriber must get each event. A queue, or pub/sub?
Loading the challenge…
While this loads — quick one
Every subscriber must get each event. A queue, or pub/sub?
As a user types into a search box, the product shows the most likely completions after each keystroke — and it has to come back within a few milliseconds, or the suggestions feel laggy and get ignored. Completions are ranked by how often each phrase has been searched before, and the catalogue of phrases is large. The read volume is enormous: every keystroke from every user is a lookup, and most of those lookups are for the same short, popular prefixes. Building and ranking the list of completions is done in the background, not on the typing path.
Every system design question opens with an account. Your design is scored the same way every time, with the reason behind each requirement, and your attempts are kept so you can see what you found hard.