Elegant Solution or Kludge?

According to those who know, SharePoint databases shouldn't get extremely large. What I gather this means, is 50 GB is large, 100 GB is very large and 200 GB is excessively large. In an industry like mine, that's not a lot of data.

Our main SharePoint litigation support application has been a big hit, and it is beyond very large and on its way to being excessively large. We present visitors to this site a "My Sites" table of contents as there are hundreds of sites but very few users are members of more than a couple sites.

With the success of the application, it is easy to foresee growth many times what it is today, so we needed a way to deal with this. Our solution is to have multiple site collections and a custom table of contents that represents them all in one place. Users create new sites self-service, so we just force them to the one site collection that is open for new cases. It's seamless to the users - they do not need to know anything about what is under the hood.

In answer to the title question "Elegant Solution of Kludge," I'll glom the two together and call it an elegant kludge. What do you think?