Please suggest is it good design to add two new different publishers for new application on single Author on existing architecture:( 1 author with 2 publishers)
Currently we are using 6.4 and on single Author we have two Publishers. Now we need to deploy one new application(different code base) on the same existing architecture. To reduce the load on Publisher we are planning to add two new Publish instances only for the new application. Please check high level diagram below( New Publish instance in blue color).
I know this is possible but will it be a better design to handle deployment activities easily in such scenario as we are two separate teams for two different applications & don't have a common Devops for deployment.
It's always better to add additional dispatchers as well (1:1 mapping). Dispatchers are commodity servers and extremely cheap to add additional ones. I would recommend to add new dispatchers to point to new publishers.
Any specific requirement to push the code bases to only few publishers? Its significantly low maintenance if you manage both the code bases on all publishers and let all publishers to handle requests for both the domains. Of course this depends on many other factors such as integrations and caching mechanisms..etc.
You just need to have site specific dispatcher configs to handle the requests from both of these sites.