
🎟️ Events, Ticketing & Creators · Database ERD
Tables for an event platform: organisers, events, venues, ticket types, orders, tickets and check-ins.
Drawing diagram…
Event platform database: organisers create events at venues; events have ticket types (early bird, VIP) with price and quantity; attendees place orders containing tickets of a ticket type; each ticket has a unique code and can have one check-in.
erDiagram
ORGANISER ||--o{ EVENT : creates
VENUE ||--o{ EVENT : hosts
EVENT ||--|{ TICKET_TYPE : offers
ATTENDEE ||--o{ TICKET_ORDER : places
TICKET_ORDER ||--|{ TICKET : contains
TICKET_TYPE ||--o{ TICKET : "issued as"
TICKET ||--o| CHECKIN : "scanned in"
ORGANISER {
int id PK
string name
string gstin
}
VENUE {
int id PK
string name
string city
int capacity
}
EVENT {
int id PK
int organiser_id FK
int venue_id FK
string title
datetime starts_at
}
TICKET_TYPE {
int id PK
int event_id FK
string name
decimal price
int quantity
}
ATTENDEE {
int id PK
string name
string email
}
TICKET_ORDER {
int id PK
int attendee_id FK
decimal total
string status
}
TICKET {
int id PK
int order_id FK
int ticket_type_id FK
string code
}
CHECKIN {
int id PK
int ticket_id FK
string gate
datetime scanned_at
}A ticketing platform built for big on-sales: a virtual waiting room, seat holds, anti-bot checks, payments and mobile tickets with rotating QR codes.
How attendees get into an event quickly: QR scan at the gate, validity check that works even if the internet drops, and a live attendance count.
A platform where creators sell monthly memberships with exclusive posts, videos and community chat, and get paid out monthly.
How user posts on a social or creator platform are moderated: automatic checks, human review of doubtful content, and appeals.
The states of a ticket order, from seat hold through payment to use at the event, including refunds when an event is cancelled.
Where a mid-sized creator's monthly income comes from and where it goes, in thousands of rupees, to plan a sustainable creator business.