Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

Dispatcher : do I now need a farm per virtual host?

Avatar

Level 7

hi folks,

I've always put my virtual hosts into a single publish farm (the /virtualhosts part)

 

Is it still o.k. to do this for new virtual hosts.?

 

There is some dispatcher documentation showing a farm per virtual host. However all my existing sites are not done like this. I assume I don't have to ?.

 

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-d...

 

thanks

Fiona

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@fionas76543059 , It is a good practice to have separate farms for each vhost. This would give you better control over caching rules and invalidation.

View solution in original post

6 Replies

Avatar

Community Advisor

Hi @fionas76543059,

 

Using multiple virtual hosts in a single farm file is fine as long as all the tenants/virtual hosts have identical configuration in terms of renders, cache, filters, statistics and other parameters.

Separating out farm files per virtual hosts usually give more control (modularity) and takes care of the Single Responsibility principle in my opinion.

 

Thanks,

Rohan Garg

Avatar

Correct answer by
Community Advisor

@fionas76543059 , It is a good practice to have separate farms for each vhost. This would give you better control over caching rules and invalidation.

Avatar

Community Advisor

Hello @fionas76543059 

 

As per Adobe's recommendation, we should modularize the dispatcher configs. It provides following benefits:

  1. Modularity and maintainability: Having separate configuration files for each virtual host allows for easier management and updates. You can modify or add new virtual hosts without affecting others, improving modularity and making it easier to maintain the configuration.

  2. Granular control: With separate configuration files, you have more control over individual virtual hosts. You can define specific rules and settings for each host independently, tailoring the configuration to their unique requirements.

If you planning to use AEM as a Cloud Service or Cloud manager, its recommended to adapt to Adobe's recommended structure. It will assure your deployments don't fail any rule, also it becomes easier for support team to debug incase of any issues.

 

Modular structure of dispatcher

 

 


Aanchal Sikka

Avatar

Employee Advisor

Hi,

 

  1.  Having multiple virtual hosts within a single publish farm can be simpler to manage and maintain, especially if you have a smaller number of virtual hosts.

  2. If you have specific security or performance requirements for each virtual host, separating them into individual farms can provide better isolation and control.

  3. If you anticipate significant traffic or resource demands on specific virtual hosts, having separate farms can offer better scalability by allowing you to allocate resources independently.

  4. Separating virtual hosts into individual farms can provide flexibility in terms of customization, caching strategies, or configuration options specific to each virtual host.

Ultimately, the choice depends on your specific needs, the complexity of your setup, and the expected growth of your environment. If your current approach of having multiple virtual hosts within a single farm is working well and meets your requirements, there may not be a need to change it.

Avatar

Community Advisor

@fionas76543059  I agree with solution from @Rohan_Garg @shubhanshu_singh Even its a best practise to have a seperate farm files for every domains until you don't have seperate configrations.