The scenario
A wedding hall management platform tracks customer bookings, hall reservations, event details, external suppliers, add-on amenities, and payments.
What is in this drawing
Read the decisions behind it.
01
Modeled bookings as separate from events to allow one booking to schedule one event and collect payments.
02
Used junction tables BookingAmenity and EventSupplier to resolve many-to-many relationships.
03
Made booking and amenity composite primary keys in BookingAmenity, and event and supplier composite PKs in EventSupplier.
Reusable for venue, banquet, or event management systems that need booking, supplier, and add-on service tracking.
More like this