You CAN have more than one Domain Index within one domain.
In our production environment, we have one domain across several locations. Each location has a separate domain index on its server, indexing locally available data(bases) only. This and the index update interval can be configured in the server document(s).
Provided the searching user is authenticated the search result list will only contain results which the seraching user has access to. The indexing server must have also read access to the indexed documents. Consider a GlobalReaders role in the reader field, assigned to the LocalDomainServers group.
I expect performance should be ok if you dedicate a server to blogs and index and activate SCT for the blog template, and/or you move static content (images and so on) to a single resources NSF or even to file system.
@Matjaz and @Philip
You CAN have more than one Domain Index within one domain.
In our production environment, we have one domain across several locations. Each location has a separate domain index on its server, indexing locally available data(bases) only. This and the index update interval can be configured in the server document(s).
Provided the searching user is authenticated the search result list will only contain results which the seraching user has access to. The indexing server must have also read access to the indexed documents. Consider a GlobalReaders role in the reader field, assigned to the LocalDomainServers group.
I expect performance should be ok if you dedicate a server to blogs and index and activate SCT for the blog template, and/or you move static content (images and so on) to a single resources NSF or even to file system.