1. Confidential – Oracle Internal/Restricted/Highly Restricted

3. How Rabobank is using Oracle API Platform Cloud Service to Achieve API Success
CAS4501
This is a Title Slide with Picture and Product, Service, or Industry Logo slide ideal for including a picture and product/service/industry or org logo with a brief title, subtitle and presenter information.
To Replace the LOGOs on this sample slide:
Right-click a sample LOGO and choose Change Picture. Navigate to the location where the new logo is stored, select desired logo file and click on the Open button to replace the sample logo.
The Presented with FPO logo placeholder box can be copy and paste to any of the Title Slides.
Xander van Rooijen – Rabobank
Robert Wunderlich – Oracle
October 25, 2018
Confidential – Oracle Internal/Restricted/Highly Restricted

4. Integrating an ever expanding financial landscape
API Management
Integrating an ever expanding financial landscape
Xander van Rooijen – Business Architect CIOO Strategy, Data & Architecture

6. Mission, vision & strategy

7. Rabobank at a glance (1)

8. Rabobank at a glance (2)

9. What is happening around us?

10. New technology and regulations are impacting the future of banking
Artificial Intelligence & Machine Learning
Cloud computing
Blockchain
Internet-of-Things & Big Data
Robotics
Biometrics

11. Open Banking
Open Banking is a financial services term as part of financial technology, driven by PSD2, that refers to: “The use of OpenAPIs that enables third party developers to build applications and services around the financial institution, resulting in greater financial transparency options for account holders ranging from open data to private data”
PSD2 implementation will mandate European banks to open up their financial services (via APIs) for their customers and licensed third party players (TPPs) – including external developers as well as FinTech players – who will use their infrastructure to build new innovative solutions on top. TPPs will be able to not only aggregate customer data, but also originate payments from customer accounts.

12. Open banking brings different engangement models

13. Digital transformation through Open Banking

14. …. brings integration challenges

15. … which will only become even more challenging

17. So where are we now?

18. We have made some good progress with digitalization and innovation

19. We have made choices in our Cloud strategy….
Cloud Service Providers
Application development
We have switched from a cloud technology first approach to a public cloud first approach

20. …. and are anticipating on bringing these worlds together
Management & Design / Catalog
iPaaS
API Management
API Design
API Management Gateway
API Management Gateway
API Management Gateway
Business Event Bus
Logic Apps / Service Bus
Step Functions
Functions
Lambda
Applications
Applications
Implementing API Platform Cloud Service and Oracle Integration Cloud (amongst other technologies)
Application
Application

21. Architecture Governance: Inbound: Outbound: Internal: Public API’s
Request
Public API’s
Private API’s
Partner API’s
Governance:
Centralized management
Inbound:
Exposing Rabobank API’s (Public, Private and Partner)
Outbound:
Exposing external API’s for the internal application landscape (Public and Private)
Internal:
Internal API’s for internal application usage only
Inbound API Gateway
Governance
Domain A
Domain B
Domain C
Internal API Gateways
Domain Servicebus
Domain Servicebus
Domain Servicebus
Request
Outbound API Gateways
Public API’s
Partner API’s

22. Use-case: Omnibanking
Integrate payment accounts from other banks in the Rabobank Online banking experience

23. Use-case: Surepay
By adding name versus account check, payment fraud is minimized
Name / account relation is provided by multiple dutch banks

24. Identity Cloud Service
API Platform
API Design
Identity Cloud Service
API Developer Portal
API Management Portal
Internal Test Gateway
Internal Production
Gateway
External Production
Gateway
BankingContactCloud
Gateway
GatewayNode – 1
GatewayNode – 1
GatewayNode – 1
GatewayNode – 1
GatewayNode – 4
GatewayNode -2
GatewayNode – 2
GatewayNode – 2
GatewayNode – 2
GatewayNode – 5
GatewayNode – 3
GatewayNode – 3
GatewayNode – 3
GatewayNode – 6
Datalake
Datalake
Financing
Financing

25. Organization & Way of Working
API Enablement team
User Management
Manage Platform
Manage shared Gateways
DevOps teams (API Providers)
Manage the API Implementations for their APIs
Manage API Deployment
Manage Subscriptions
API Monitoring
Manage dedicated gateways (optionally)
The primary focus is to enable DevOps teams to deliver their functionality faster, doing it themselves.
Do it
Together
Do it
Yourself
Demo

26. We see a big increase on API usage!
Gateway
# APIs
(May18)
# Apps (May18)
#Load (May18)
#APIs (Oct18)
#Apps (Oct18)
#Load (Oct18)
Internal Test Gateway 11 17
15.000
53 (+482%)
35 (+206%)
(+345%)
Internal Production Gateway 7 12
26(+371%)
28 (+233%)
(+554%)
External Production Gateway 6 4 -
15(+250%)
13 (+325%)
53.100
BankingContactCloud Gateway 1 2
Cloud – OnPremise 20 15
8.068
# May18
# Oct18
Published APIs in Portal 14 23
+164%
API Implementations in Console 73
+317%
Feature Teams – API Providers 10 44
+440%
Feature Teams – API Consumers 16 56
+350%

27. But we are not there yet…..

28. To enable Open Banking, we need to further evolve our integration architecture …
PERSONAS
ENDPOINTS
INTEGRATION PATTERNS
DEPLOYMENT MODELS
Where integration specialist had pre-dominantly designed and delivered integrations, business users and other IT staff can now perform integrations themselves. This is made possible by the uprising of SaaS applications, which deliver standardized API's for inter-operability.
Applications will reside in the Cloud, on-premise, mobile apps and even things (IoT devices). We must support secure connectivity to the endpoints these applications will expose.
With the addition of Cloud and things, new patterns have emerged. We now need to think about not only connecting applications within our own datacenters, but also:
Cloud 2 Cloud
Cloud 2 Ground
Intra Cloud
The expanding landscape will also challenge our deployment models. Integration will not solely be executed on-premise, but will move into the cloud. Where will they be deployed and how?
Shifting the perception of integration from a "back office" function to a front-line digital business competency, enabling business innovation and competitive differentiation through integration of semi-commoditized digital systems

29. … while trying to constrain complexity

30. Future Outlook Defining a new way of API First API Strategy Definition
Training
PSD2 / GDPR
Platform
Multi Cloud
Developer Experience
Decide on an uniform approach and
definition of our API’s
Deliver a seamless DX for any developer, both external and internal
Strengthen the knowledge of API’s and their usage within the organization
Management of API’s and gateways across different
eco-systems
New legislation will require new levels of consent management
Adjust the platform technology to the API strategy

31. Thank you for your attention

32. Learn More about API Management
Explore
Learn
Discuss
Here are some important links to get more help.

33. apiary +
365,802
API Designers
470,440
APIs
5.5M+
API Consumers
- Background: Built APIs & Services for 10 years
- Built tooling for APIs at Apiary, acquired by Oracle
- Successful at it: Numbers
Confidential – Oracle Internal/Restricted/Highly Restricted