Single Author with two different Publishers : will it be a good Architecture design? | Community
Skip to main content
sunily21159739
Level 2
Apr 9, 2021 10:09 PM UTC
Solved

Single Author with two different Publishers : will it be a good Architecture design?

Hi All,

 

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.

 

Thanks,

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
joerghoh
joerghohAccepted solution
Employee
Apr 10, 2021 6:37 PM UTC

Deployment is one problem, the interaction between the 2 codebases a different. And if you are working on-prem, licensing might be a third.

 

On author you need to have the 2 codebases running in parallel, and that very like needs some kind of coordination and testing. To have maximal separation between these 2 applications you should have distinct environments. See also my blog posts about multi-tenancy:

 

https://cqdump.joerghoh.de/2015/05/04/the-problems-of-multi-tenancy-governance/ 

https://cqdump.joerghoh.de/2015/06/23/the-problems-of-multi-tenancy-the-development-model/

 

 

9 replies

joerghoh
joerghohAccepted solution
Employee
Apr 10, 2021 6:37 PM UTC

Deployment is one problem, the interaction between the 2 codebases a different. And if you are working on-prem, licensing might be a third.

 

On author you need to have the 2 codebases running in parallel, and that very like needs some kind of coordination and testing. To have maximal separation between these 2 applications you should have distinct environments. See also my blog posts about multi-tenancy:

 

https://cqdump.joerghoh.de/2015/05/04/the-problems-of-multi-tenancy-governance/ 

https://cqdump.joerghoh.de/2015/06/23/the-problems-of-multi-tenancy-the-development-model/

 

 

Translate
sunily21159739
Level 2
Apr 12, 2021 9:24 PM UTC
thanks @joerghoh
Translate
Singaiah_Chintalapudi
Level 7
Apr 9, 2021 10:38 PM UTC

Few things to consider:

  1. 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.
  2. 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.
  3. You just need to have site specific dispatcher configs to handle the requests from both of these sites.

Thanks,

Singaiah

Translate
sunily21159739
Level 2
Apr 9, 2021 11:01 PM UTC
Thanks Singaiah for your response, yes we we need to keep separate both the code base, First application code on one Publisher(4503) and second application code on New Publisher(4505). Since Author will still be shared between application one and application two do you believe it could cause bottlenecks based on the DevOps pipeline and coordination with separate development teams and timelines.
Translate