Book Shop System Design | Dataford Interview Questions

Your question is Book Shop System Design. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

HLD + LLD of a Book shop: requirements, scale, database choice, class design (coded), concurrency, and supporting fines as a future use case.

Asked in the onsite design stage. Reported follow-ups included Elastic Search, DynamoDB streams, and support for fines.

Address the following:

Clarify functional and non-functional requirements.
Estimate scale and choose storage for books, inventory, orders, users, and fines.
Define the high-level architecture and consistency boundaries.
Provide class designs and code for core operations.
Explain concurrency control for checkout, inventory, and payments.
Show how Elastic Search, DynamoDB streams, and future fines fit without coupling the domain model.

Your question is Book Shop System Design. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

HLD + LLD of a Book shop: requirements, scale, database choice, class design (coded), concurrency, and supporting fines as a future use case.

Asked in the onsite design stage. Reported follow-ups included Elastic Search, DynamoDB streams, and support for fines.

Address the following:

Clarify functional and non-functional requirements.
Estimate scale and choose storage for books, inventory, orders, users, and fines.
Define the high-level architecture and consistency boundaries.
Provide class designs and code for core operations.
Explain concurrency control for checkout, inventory, and payments.
Show how Elastic Search, DynamoDB streams, and future fines fit without coupling the domain model.