member, school, schoolclass, student, member-availability, scheduling-period, schoolclass-availability, scheduled-session.@code {} part of my razor files, which feels OK-ish, but once the queries get big, it feels for me that I am cluttering database interactions in the UI. Additionally, when I am using different DB operations my @code {} block becomes extremely large. I could implement a repository pattern, which creates a layer of separation in my code, and thereby makes my razor files a bit neater. But since EF on its own already has some form of a repository pattern in its framework, it feels that I am creating duplication.