On Prem servers are needed to Support Financial Reporting
Change Request Description:
This change request proposes migrating our core financial reporting servers from the current cloud infrastructure to an on-premises deployment. During month-end processing, the financial team experiences severe database latency, delaying critical financial closures and reporting deadlines. Our analysis indicates this bottleneck is driven by high-volume data transfers and API calls traversing external networks.
By relocating the reporting servers on-premises—physically adjacent to our primary local data warehouses—we will drastically minimize network hops and eliminate cloud egress bottlenecks. Testing estimates indicate a 60-70% reduction in query latency, which will streamline data processing and ensure month-end reports are generated within expected SLA windows.
Change Impact:
Implementing this change transitions our financial infrastructure into a hybrid cloud model. While core transactional processing and public-facing applications remain securely in the cloud, the heavyweight reporting engine will operate locally.
This architecture requires establishing a dedicated, encrypted VPN tunnel or direct connect line to maintain secure, continuous data synchronization between cloud databases and on-prem storage. The primary technical challenges include managing cross-platform identity access management (IAM), configuring local firewalls to permit real-time data replication, and monitoring network bandwidth to ensure the hybrid bridge does not become a new point of failure.
Change Logs & Notes
| Date | Owner | Note |
|---|---|---|
| 07-10-2024 | Chris Freeman | This plan follows our original concern of month-end closing issues, so leadership fully supports the move. Servers are being repurposed for the 2024 Modernization effort. |