5.3.2 Production Deployment Recommendations

isolated computing environments, which helps mitigate the risks associated with change and contributes to the delivery of stable, extensible, and high performing business capabilities.

User acceptance testing, performance testing, load testing, and training are often performed in the safety of a staging environment without the risk of negatively impacting the production system. The City may choose to implement each of these activities in separate computing environments instead of in a single staging environment.

5.3.2 Production Deployment Recommendations As noted in section 5.2.3, the Cloud infrastructure in Azure offers a flexible and scalable platform. Miramar will be able to deploy a single external URL while maintaining isolation of the organizational and police subnetworks. The specific recommendations are provided here, including a diagram illustrating the isolation of the two subnetworks.

Miramar Organizational Subnet • 1-Node Web Server: Azure D2V3 2-core, 8GB RAM (Web Adaptor) • 1-Node GIS Server: Azure B4MS 4-core, 16GB RAM (ArcGIS Enterprise) • 1-Node Portal Server: Azure B4MS 4-core, 16GB RAM (Portal for ArcGIS) • 1-Node Data Server: Azure B4MS 4-core, 16GB RAM (PostgreSQL, Relational

Data Store) • 1-Node Desktop: Azure D2V3 2-core, 8GB RAM (ArcGIS Desktop) • Optional: 1-Node Data Server: Azure B4MS 4-core, 16GB RAM (Tile Cache Data

Store)

Miramar Police Subnet • 1-Node Web Server: Azure B4MS 4-core, 16GB RAM (Web Adaptor, Portal for

ArcGIS) • 1-Node GIS Server: Azure B4MS 4-core, 16GB RAM (ArcGIS Enterprise, ArcGIS

Desktop) • 1-Node Data Server: Azure B4MS 4-core, 16GB RAM (PostgreSQL)