This document in the Google Cloud Well-Architected Framework describes principles and recommendations to help you to design, build, and manage financial services (FS) applications in Google Cloud that meet your operational, security, reliability, cost, and performance goals.
The target audience for this document includes decision makers, architects, administrators, developers, and operators who design, build, deploy, and maintain FS workloads in Google Cloud. Examples of FS organizations that could benefit from this guidance include banks, payment infrastructure players, insurance providers, and capital market operators.
FS organizations have specific considerations, particularly for architecture and resilience. These considerations are primarily driven by regulatory, risk, and performance requirements. This document provides high-level guidance that's based on design considerations that we've observed across a wide range of FS customers globally. Whether your workloads are fully in the cloud or transitioning to hybrid or multi-cloud deployments, the guidance in this document helps you design workloads on Google Cloud to meet your regulatory requirements and diverse risk perspectives. The guidance might not address the unique challenges of every organization. It provides a foundation that addresses many of the primary regulatory requirements of FS organizations.
A primary challenge in designing cloud workloads involves aligning cloud deployments with on-premises environments, especially when you aim for consistent approaches to security, reliability, and resilience. Cloud services create opportunities to fundamentally rethink your architecture in order to reduce management overhead, optimize cost, enhance security, and improve reliability and resilience.
The following pages describe principles and recommendations that are specific to FS workloads for each pillar of the Well-Architected Framework:
- FS perspective: Operational excellence
- FS perspective: Security
- FS perspective: Reliability
- FS perspective: Cost optimization
- FS perspective: Performance optimization
Contributors
Authors:
- Gino Pelliccia | Principal Architect
- Alex Stepney | Lead Principal Architect
- Phil Bryan | EMEA FSI Lead Principal Architect
- Stathis Onasoglou | EMEA FSI Principal Architect
- Sam Moss | EMEA FinOps Professional Services Lead
Other contributors:
- Daniel Lees | Cloud Security Architect
- Danielle Fisla | US FS Portfolio Lead, PSO
- Filipe Gracio, PhD | Customer Engineer, AI/ML Specialist
- Henry Cheng | Principal Architect
- John Bacon | Partner Solutions Architect
- Jose Andrade | Customer Engineer, SRE Specialist
- Kumar Dhanagopal | Cross-Product Solution Developer
- Laura Hyatt | Customer Engineer, FSI
- Michael Yang | Industry Solutions AI Consulting Lead, FSI
- Nicolas Pintaux | Customer Engineer, Application Modernization Specialist
- Omar Saenz | EMEA Partner Engineer, Security
- Radhika Kanakam | Program Lead, Google Cloud Well-Architected Framework
- Steve McGhee | Reliability Advocate
- Tarun Sharma | Principal Architect
- Yuriy Babenko | Customer Engineer, FSI