You should avoid multisite unless it’s clear that is what is required. It’s meant for separate users to be able to manage their own subsites. If you are managing all content anyway, it’s unlikely you really need multisite. Generally the various content can be served dynamically based on a user’s specific needs. Content can be tagged for a certain language and region and queries can be qualified by these tags so users only see appropriate content.
I use the term “tag” loosely here. I don’t specifically mean the post tag taxonomy terms, though that remains a possibility. Any sort of taxonomy term or meta data could be used to qualify queries. Give some serious thought to how the data will be organized because it becomes more difficult to change concepts as the volume of data involved grows.
An elaborate data schema will likely involve some custom coding to pull it all together. There are plugins available that will ease the burden, but usually some custom work is needed to tie it all together.
There’s a range of opinions on this matter. I’d expect someone to come along and legitimately claim that multisite is the way to go. Every site has distinct needs and every site developer has different abilities to bring to the table. There is no one best solution for everyone. Collecting thoughts on the matter is good, but only you can decide what’s best for you.
Thank you bcworkz for your time and information.
I totally agree with your approach, will study the case to choose the best configuration
