Event registration: sub-pages oder structure?

The CMS Questions
1

I am currently working on an event registration and am basically following the cookbook recipe “EventKit”. (Create pages from frontend | Kirby CMS)

I expect between 30 and 150 registrations per event. In addition to the EventKit, I will implement a page with a tabular overview of all registrations and a function to export the registrations as CSV.

What bothers me a bit about the EventKit is that the individual registrations are saved as subpages of the event page. I would find it “handier” if I could store the registrations in a structure field in the event page.

My question: Are there any reasons against saving the registrations as a structure? General performance? Handling of the data in tabular display or export?

I would be very grateful for your assessment.

2

When you use a structure field for registrations, there is a certain risk of data loss.

When you use a structure field, you need to update the page with the new registration every time a user registers. Which means, you need to fetch the current entries into an array, add the new entry, then save the new field value to the page. This can be a bit risky in case of concurrent registrations.

3

Thanks a lot Sonja, very good point! I‘ll stick with sub-pages.