Summary: Designing the Amazon Locker Service
Learn to analyze the Amazon Locker Service design by reviewing its key requirements, core classes, and object interactions. Understand how SOLID principles and design patterns like Strategy and Repository enhance system scalability, maintainability, and secure access management through real-world workflows.
Now that you’ve completed the Amazon Locker service case study, let’s take a moment to reflect on and consolidate what we’ve learned. We’ll revisit the key system requirements, identify the core classes along with their responsibilities and relationships, and highlight the major design principles applied. We’ll also examine how objects interact within the system and walk through the overall workflow to understand how the components come together to achieve the desired functionality.
Key requirements
Here is a list of the primary functional requirements for the Amazon Locker system.
Customers can select a preferred locker location for order pickup during checkout.
Orders can contain multiple items packaged together based on locker size availability.
Locker locations have multiple lockers of various sizes.
Only packages within a locker’s dimensions are eligible for locker delivery.
Customers receive a unique code to open the locker when a package is delivered.
Packages are held in a locker for a maximum of three days.
Package pickup must occur within the three-day window and the locker location’s operating hours.
After three days, uncollected packages are removed, the locker is released, and a refund is initiated.
Each locker can only be assigned to one customer/package at a ...