Hi,

Pega cloud 2.x architecture kept these as a separate node. The benefit of keeping this separate :

1) Load management

2) If anything happen and these nodes went down, the web node is separate and production user will not get affected.

3) Easy to maintain.

I dont see any big cons in this. Only one thing that if we dedicate a resource and if we are not using it then it is kind of unnecessary waste of resource. 

I also recommend you to keep this as a single machine per each tier type. 

For example, util node takes care of all the indexes, and if you will process a lot of data, that machine will take that responsibility mainly and other tiers will be not overloaded. 

You need to consider if you will scale that environment, how it will be hosted (cloud, traditional approach).  There is also solution to prepare docker image for each tier type, and use it in the cluster behind Load Balancer so you can easily scale in/scale-out environment without downtime. 

@SVAQuest, good question here. Keep in mind that Pega cloud environments are fully managed by Pega and you should work with Pega cloud experts for any sizing/tuning recommendations.

Hi Kelvin,

Thanks for the details.  I had got the supporting details from Pega cloud team and came to know that this tiers are placed to improve the performance based on the specific customer needs.

Regards
SVAQuest