I have an architecture similar to this:
User (Name, Email, ID...) ---- Studios (Name, Location, Description...) ---------- Videos (Title, Description, URL, Length, Views...)
Simply put, a user can have 1 to multiple studios and a studio can have 1 to multiple videos.
Each of these are Classes in my PHP application (User, Studio & Video) that stores information (User name, User ID, Studio name, Studio location, Video name, Video URL, Video views...)
Right now, if I want to show, for example, the total amount of videos & views that a user has considering all of his content, I build all of his Studios from the User Class (with a function like "build_Studios", then for each Studios I build all of the Videos from the Studio class (with a function like "build_Videos".
This allows me to easily access any data that I need rather easily, however now that I am looking at the length of our data, I am a bit skeptical about this approach. For example, one user can easily have posted in the range of thousands of medias spread across his Studios. Also, I am now thinking about the Pagination feature which seems like it would make much more sense using LIMIT instead of parsing an array...
So I would like to know if I should review my architecture while the project is still at an early stage. If so, how would you recommend that I organize my data? Otherwise, is a structure like the one I cited previously proper for a large application?