The scenario
Designing a database for a monthly subscription clothing rental service where users pick a plan, rent garments per order, and make payments.
What is in this drawing
Read the decisions behind it.
01
Use separate Payment entity to support multiple payments per order
02
GarmentCategory ensures organized garment inventory
03
CustomerSubscriptionPlan is directly linked via plan_id FK
When modeling a subscription-based rental system needing a normalized schema with orders, garments, and payment tracking.
More like this