SRS Service best practices
We have been reading Pega's documentation around SRS for connecting to externalized Elastic Search. We are planning on having a shared Elastic Search per Environment and We are looking to create a separate namespace for the SRS instances (also one per environment) for all Pega Applications to connect. We want to know Pega's recommendation on whether SRS Service be deployed on the same namespace as Elastic Search or having them separated (pros and cons that you can provide).
Example: Namespace Namespace Namespace Pega app1 Dev SRS Dev Shared Elastic Search Dev Shared Pega app 2 Dev SRS Dev Shared Elastic Search Dev Shared VS Pega app1 Dev SRS and Elastic Search Dev Shared Pega app2 Dev SRS and Elastic Search Dev Shared Thanks,
Steven
Eclatprime Digital Private Limited
SG
Steven as part of pega docker image srs and elastic search is part of backing services so using single namespace yes we can able to deploy and get the pods running but you need to update the pod url linking in your application deployment yaml so that i can establish the link btw application and srs