Im on a project in which i will have a lot of pages and also users. I did already a topic for the pages and i was able to solve this via DB solution. https://forum.getkirby.com/t/performance-createchild-vs-pageobject/18431/4
now. im in the same situation as i was in the pages problem. as soon the user count is more than 2000 users, the loading time in some situations are not so good. there is already a frontend login part, and im using kirby user session to upload/modificate content on the page/db. users are just for frontend login/auth, no panel login needed.
this is all working find but speed and scalability matters. because the project will be public i need a solution to handle this, so the user-part should also be scaleable. my best guess is switching to DB.
- Saving all users would be an easy task over an api and DB integration.
- My problem/question is, how can i highjack the way kirby is loading the users from DB instead of the filesystem? Because this is an important part of the system, im prefer not to hack this in some way but looking to an more official way to do so.
Maybe someone have advice how this can be done? @bastianallgeier
Thanks!