Not quite sure with your question here; are you creating two separate repositories ?
Do you mean separate CRX and CQ ? or are you creating two workspaces?
Thanks for your response.
Yes i mean separate CRX to store document high level architecture will be as below
I have done the POC all working fine. By moving contents to another CRX server we will significantly reduce completion time of indexing, backup , garbage collector and tar optimization jobs on AEM server as a result we will improve performance and reliability. I am wondering how others companies are managing large CQ repository in other organization.
We have done Scene7 for one of the biggest retail clients in uk. You will require an additional license for this. Essentially your images are stored in cloud ('scene7'). You release your images to scene7 according to a plan. When your public page loads scripts will pull your images from your cloud provider by providing a client code. You can also get renditions on the fly. If you evaluate this you have everything covered . Other alternatives are other cdn providers like akamai. Renditions on the fly is a winning feature of Scene7.
Some thoughts and pointers :
1) I agree you will see some performance gain however on reliability you need to consider clustering.
2) I would give some consideration to users, ACL, backup and maintenance as we add repositories (Should not be big deal)
3) Consider authoring workflow with synchronization & version (how documents are uploaded on regular basis along with page and templates etc)
4) Development and testing considerations for two repositories.