Jump to content

Recommended Posts

Posted

I’m building a simple ticket booking system for our events. I’m considering two different solutions:

The first approach is creating one page per ticket and a reference to a booking page with the contact info. This should be faster when checking for ticket availability by using $pages->count().

The other one is a one page per booking with an integer field holding the ticket quantity. Downside is having to use $pages->find() but only having to create one page per booking with the API. 

My biggest concern is listing the events and the ticket availability for each event, loading all bookings.

At the most one event has 300 bookings.

Any ideas are welcome.  

Posted

In a similar scenario, I update a free ticket counter field on the event page whenever a booking is made. This works for both solutions and enables a blazing fast search.

  • Like 2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...