Loading page…
One strong interview answer to "design bit.ly": a read-path problem with a tiny write path, codes from leased ID blocks scrambled and base-62 encoded, 302 redirects made cheap with cache-aside, negative caching and async click counts, and what to do when Redis or the allocator fails.
The interviewer slides a marker across the table and says: design bit.