How to publish map services in a Blue-Green deployment architecture for ArcGIS Enterprise?

[VenkataKondepati]

We are implementing a Blue-Green deployment model in AWS for our applications and APIs, where new versions are deployed to a secondary environment, tested, and then promoted by switching traffic over.

For our GIS component, we need to publish ArcGIS map services (developed with ArcGIS JavaScript + ArcGIS Enterprise services) as part of each release cycle. My question is:

• What is the recommended way to publish or update map/feature services in a Blue-Green deployment setup?

• Should services be published to both environments in parallel, or promoted only after validation?

• How do we handle dependencies like data store registration, service item IDs, and Portal content references when flipping between Blue and Green environments?

• Are there best practices to ensure zero/near-zero downtime and avoid broken service URLs for end users during cutover?

Any guidance, patterns, or references from those who have implemented Blue-Green deployments with ArcGIS Enterprise would be very helpful.

Thanks in advance!

[sxw_eaglegis]

Hi there,

Some information and best practices is described here - https://enterprise.arcgis.com/en/portal/latest/administer/windows/overview-disaster-recovery-replica...

The standard approach would be to use the WebGISDR tool to replicate all content between sites. The two sites would be setup and configured the same way, so would have the same data store registration, item IDs etc. The tool does not copy data from databases or folders, so if you have non hosted data this would have to be replicated using a different process. How often is the data updated?