Discussion

73
Views
Close popover
Anuj Thomas Mathew (ANUJTHOMAS)
Link Asset Services

Link Asset Services
IE
ANUJTHOMAS Member since 2011 4 posts
Link Asset Services
Posted: November 30, 2020
Last activity: November 30, 2020

Splitting Pega instance into separate smaller applications

Hi all,

Wanted to start a discussion on a path that my organisation DevOps is proposing that Pega takes. Our Pega instance consists of 4 applications built on a reusable Org layer (built on CS). Each application caters to a separate line of business.

The DevOps team is proposing splitting the instance into separate containers for each application citing conflicting maintenance periods affecting other applications and general maintenance being difficult. While I understand where they are coming from, is this the suggested way? I am torn between the advantages and the disadvantages - mainly the cost in separate app servers/SQL servers and trying to ensure reusability across the applications. There is also the danger of each application moving on to a separate development direction from each other, which isn't ideal either (in my head).

I know that going the route of reusable component application will solve the reusability issue (to some extent) but I just wanted to ask you all on your opinion on this. Is it the preferred way to go and if yes, why? Are there any alternatives to such scenarios? Maybe multi-node with each node specific to a line of business?

Appreciate your thoughts on this.

Pega Customer Service for Financial Services 7.31 Pega Platform Case Management DevOps Financial Services Lead System Architect