Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

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

Avatar

Avatar
Ignite 1
Level 1
sunily21159739
Level 1

Likes

2 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Ignite 1
Give Back
Boost 1
View profile

Avatar
Ignite 1
Level 1
sunily21159739
Level 1

Likes

2 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Ignite 1
Give Back
Boost 1
View profile
sunily21159739
Level 1

09-04-2021

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).

sunily21159739_0-1618005209781.png

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,

 

View Entire Topic

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,113 likes

Total Posts

3,145 posts

Correct Reply

1,072 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,113 likes

Total Posts

3,145 posts

Correct Reply

1,072 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

10-04-2021

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/