My suggestion would be to have a main central 'registration' database where the students would sign-up for their blog. Code in that registration process would add the user to an existing shared blog database (say 10 users per) or a new one if the limit was exceeded (maintained in profile docs).
And for the 'latest entries' issue, make an agent part of the blog submission that qualifies a blog entry (access for all to read) and then sends every new entry to that Main registration db.. From there you can keep the last 50 submitted and delete the rest on a scheduled basis.
My suggestion would be to have a main central 'registration' database where the students would sign-up for their blog. Code in that registration process would add the user to an existing shared blog database (say 10 users per) or a new one if the limit was exceeded (maintained in profile docs).
And for the 'latest entries' issue, make an agent part of the blog submission that qualifies a blog entry (access for all to read) and then sends every new entry to that Main registration db.. From there you can keep the last 50 submitted and delete the rest on a scheduled basis.