Maybe you can help me decide how suitable Domino is for a project I've been approached about.
The client is a university with about 20,000 students. They want to give each student the ability to blog. Sounds simple enough, right? Well, the more I think about the more involved it becomes. You see, each entry in each student's blog is to be access controlled. Using either people and/or groups the blogger can control who sees what they've written.
The most obvious solution is to give each student their own NSF version of the blogging template and stick some readers fields in there. Not so fast though.
For obvious reasons the client doesn't want 20,000 NSFs to look after. Not only this but the whole thing should be searchable, so using one vast NSF is the only real way to go.My concerns, which I've expressed with the client, are about how well Domino will cope with so many readers fields in a database that could potentially be quite large. However, they have an investment in Domino and most in-house admin skills are Domino-based, so they are really keen to see it work on the infrastructure they have.
Hence I've come to you guys for help. What are your thoughts? How well do readers fields perform in large views? Not just views but in the inevitable LotusScript searches needed to build content on the fly.
Even assuming half the students take up the chance to blog and only half of them do it regularly - say twice a week - we could still be looking at 1,000,000 entries per year.
How much of a factor is the server's hardware? Apparently it's quad-core and has oodles of RAM.