
🎟️ Events, Ticketing & Creators · C4 Architecture · Pro
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.
C4 Architecture diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
Concert ticketing: fans join a virtual waiting room when sales open and are let in at a controlled rate. The event catalogue service shows events and seat maps. The inventory service holds seats in Redis for 8 minutes. A bot-protection service scores traffic. The order service takes payment through a payment gateway and issues mobile tickets with rotating QR codes. Organisers manage events and see sales in an organiser dashboard.
C4Container
title Concert Ticketing
Person(fan, "Fan", "Buys tickets")
Person(org, "Organiser", "Creates events")
System_Boundary(tk, "Ticketing Platform") {
Container(wr, "Virtual Waiting Room", "Edge service", "Queues fans at on-sale")
Container(cat, "Event Catalogue", "Node.js", "Events and seat maps")
Container(inv, "Inventory Service", "Go", "Seat holds and sales")
Container(bot, "Bot Protection", "Python", "Traffic scoring")
Container(ord, "Order Service", "Java", "Checkout and tickets")
Container(dash, "Organiser Dashboard", "React", "Events and sales")
ContainerDb(red, "Seat Holds", "Redis", "8-minute holds")
ContainerDb(db, "Orders DB", "PostgreSQL", "Orders and tickets")
}
System_Ext(pg, "Payment Gateway", "Cards, UPI")
Rel(fan, wr, "Joins queue")
Rel(wr, cat, "Lets fans in")
Rel(cat, inv, "Seat availability")
Rel(inv, red, "Holds seats")
Rel(wr, bot, "Scores traffic")
Rel(inv, ord, "Checkout")
Rel(ord, pg, "Payment")
Rel(ord, db, "Saves orders")
Rel(org, dash, "Uses")
Rel(dash, db, "Reads sales")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.
Tables for an event platform: organisers, events, venues, ticket types, orders, tickets and check-ins.
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.