With recipes and the announced site templates, what are the future use cases for multi-sites?
Why we have multi-sites?
It is easy to have multiple sites that run on the same codebase. This means when a feature is added or changes have been made, it takes one deploy to update multiple sites.
With the Domain module it is possible to share users and content. The config can be fine-tuned for the different sites with Config split.
What are the multi-site problems?
When a single site is responsible for most of the resources it is harder to isolate the site resources.
When features and configurations start to divide, you have to be careful to introduce features or config to the sites that need it.
And at what time the divide is becoming to large to keep the sites together.
When the default site of the multi-sites is no longer the default, it requires configuration juggling and deploy changes.
Where can recipes and site templates help?
A site template, as I understand it, is a distribution without the problems. This makes setting up a new site a breeze.
Because it is a single site, there will be no multi-site problems in the future.
With recipes it is easy to add new features.
Recipes are only added to the sites that need them.
What are the site template and recipe problems?
When a recipe needs to be executed for multiple sites, there has to be tooling to make it as developer friendly as with a single codebase.
It is possible to share content using the Entity share module, but for users an SSO solution or a custom REST synchronization module is needed.
Conclusion
I think a single site is less error-prone, so I would opt for a site template. Building the tooling will be a one time job.
What do you think? Are you going to keep building multi-sites or go for the site template single sites?
Are there benefits or disadvantages I forgot to mention?
Top comments (0)