BBVA Secure Cloud Reference Model Responding to Complexity and Demand with a Multi-Cloud Strategy An Evaluation of BBVA’s Cloud Banking Model Pascual “Pasky” de Juan & Jose Maria “Chema” San Jose Innovation in Technologies, BBVA Digital Banking April 2015

Who we are 625 51 31 7,371 22,104 108,770 Billion € total assets million customers 31 countries 7,371 branches 22,104 ATMs 108,770 employees

Why DOES the BANK NOT HAVE Vision Why DOES the BANK NOT HAVE 1 BILLION Customers? Because IT can’t

Complexity and demand run faster than Moore's Law Exhausted Model Demand Peak dimensioning Unitary price Complexity Still running t Complexity and demand run faster than Moore's Law

Embracing Digital Transformation Agile DevOps Cloud Individuals and interactions Working software Customer collaboration Responding to change Continuous... testing delivery monitoring Automation Autoscaling Infrastructure as a code Cloning environments Complete resilience Self Provisioning Qué necesitamos A new way to grow in a worldwide scale As a faster way to update technologies Avoiding peak penalties Automating complexity management Cloud es la respuesta Cloud sets up self provisioning infrastructure Hybrid Cloud allows unlimited elasticity (no constraints) Active-Active Hybrid Cloud boosts resilience Hybrid data model (sensitive aware) ensures privacy Programmable automation simplifies management Damos un paso atrás. La transformación digital requiere de la entrega de aplicaciones dinámicas (funcionalidad en el tiempo). Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Deliver value to customers through amazing applications

Privacy and Regulatory compliance Sensitive Data BBVA Datacenter BBVA BBVA Spain Mexico USA Manage-ment & Support BBVA DMZ Z Non Sensitive Data Uno de los grandes problemas es la privacidad. Tanto en el espacio como en el tiempo. Long term transfer Amazon business model constraints Google physical constraints no constraints

Reference Model Consumers How What with Cloud Broker Security Micro Service Micro Service Micro Service Micro Service Service Management Continuous Delivery + SecDevOps Cloud Governance Model (includes Budget and Billing) Client app layer is on top over hydra layer. It is implicit the use of cloud governance. PaaS What with Orchestration IaaS SDN

Reference Model Cloud Broker Security Micro Service Micro Service Service Management Continuous Delivery + SecDevOps Cloud Governance Model (includes Budget and Billing) PaaS Orchestration IaaS SDN

Cloud Catalog (Virtual Machines, SW packages, SW Developments) New lifecycle Deployment Package Tested Deployment Package Evolved Deployment Package SecDevOps Cooperation Development Testing Production Maintenance Cloud Catalog (Virtual Machines, SW packages, SW Developments)

Cloud Designed Server-Side Apps Module-designed monolithic app Stateless Service-designed elastic app Intake Intake Intake Queue based Log Filtering Log Filtering Filtering Filtering Delivering Heterogeneous growth Delivering Infinite scalability, low latency Tetris running in Amazon will never be a cloud app

Private Cloud

Actual numbers from actual usage Amazon Anonymous service technical log 22 worldwide channels Topic Thunder 15 million events / day Hydra Actual Financial Service Technical analytics Internal Sync 300 events / s peak Google Topic Thunder Bored machines Hydra Back End Back End Back End

Lessons learned Cultural change capital PoCs very useful Concentrate on design Heavy work in role definition Build an inclusive team across different departments Adapt to consume Openstack services Work in progress and everyday learnings

And don't let cloud-like sellers fool you with “fog and mirrors”! Thank you for your attention and good luck.