Home/Low-level design/Parking Lot

Parking Lot

Compatible allocation and ticket lifecycle

Ownership and transitions

Compatibility and reservation are separate responsibilities. Rank kinds by size, then select the smallest compatible kind and ID to avoid wasting a larger resource. Ticket IDs identify ownership across release/reallocation; a repeated old release cannot free a newer occupant. Validate every inventory record before the instance becomes usable. A scan costs O(spots) per arrival; map lookup makes release expected O(1).

JavaScript boundaries

Use native classes with per-instance state and plain object/array snapshots. Object assignment shares a reference; copy retained inputs and every outward mutable container, including nested arrays. null means absence. Map handles arbitrary string keys safely, including "__proto__"; do not confuse a missing key with zero or an empty string. Domain validation uses RangeError. Numeric inputs must satisfy Number.isSafeInteger, so booleans, fractions, infinities, and NaN are invalid where an integer is required. All documented aggregate results and timestamp-plus-duration sums fit the safe-integer range. Strings use exact case-sensitive equality; lexical order compares JavaScript UTF-16 code units. Calls are serialized and synchronous.

JavaScript
const internal = ["initial"];
const snapshot = [...internal];
snapshot.length = 0;
console.assert(internal.length === 1);

A detached snapshot protects ownership; the service still has to validate and commit a coherent transition.

Put it into practice

Implement the exercise in a full-screen workspace, then run its tests.

Open practice
Next lessonVending Machine