Design a Book Price Aggregator
A book price aggregator is a middleman. It holds no books of its own. It asks bookstores and distributors what they'd charge and picks the best answer. When the price is right, it buys the book for the customer. Think of a price comparison site that also places the order. The customer identifies the book by its ISBN, the 13-digit number that names one edition of one book.
Databricks isn't a bookstore, but this is one of the distributed prompts that comes up most often in its loops. It shows up in the technical phone screen and in the onsite design round. Sometimes it's framed as a bookstore pricing API with batch lookups, or as a book buying and selling service. The product is tiny. The hard parts all run through systems you don't control: hundreds of store APIs that answer slowly or not at all, and a payment provider that can fail between two calls.
DatabricksPremium lesson · System design round
The Databricks design, worked end to end.
- The API and data modelSystem design · Signature problem
- The design, drawn out2 diagrams
- 5 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
106 Databricks interview reports · guide updated
Databricks interview guideKnow what Databricks asks before you walk in.
22 coding · 5 system design · 28 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.