How to build the right architecture?

Question

Database design

Hello. There is an event module. The task of the module is to publish events, create registration (accept applications). Like Yandex poster. Types of events: competition, master class, battles, courses, etc. Each type can have distinctive data. For example, a lecturer is required for a master class. Each event can take place in several periods: one-time or on certain dates - March 21 and April 1, December 5, etc.

For example, there is the Olympiad of Arts event, it has its own poster and other data. Within the framework of which it takes place: a festival of amateurs, a master class in acting skills "Grace", and courses for teachers "stimulus".

All these types have their own registration system. All types are united under one common event Olympiad of Arts. But there are not always so many subtypes.

How can I better combine and display all types in one event?

I assume that it will be necessary to create an event. Then create types for this event: festival, course, master class. Am I thinking right? What would you do? how to do it better?

Answer 1

Any event or event is a graph node.
Node - has its own type and contains its own properties depending on the selected type.
Nodes have connections.
To control the nodes of the entire graph, an event observer is created.
It monitors the correctness of the statuses and integrity of related/dependent events.
Also, it keeps a historical log of status changes: open / completed, and other indicators of events.
Any other objects simply have links by identifier with the desired node in the "tree" of events (for example, a lecturer).