Niels Zegveld, Manager, Engineering Database and Middleware of Rabobank, presented a case study at Postgres Vision 2018 that explained building a new Database-as-a-Service (DBaaS) with EDB Postgres so that IT managers would no longer have to interact with the OS.

1. DOC ID
1
Introduction Rabobank

2. DOC ID
2
Database as a Service
What is database as a service (DBaaS) generically?
• A self-service computing environment offering the ability to create, consume and pay for
database services.
• Computing resources are elastically supplied from a shared pool and charged based on metered
use.
• Intrinsically secure and compliant
• Service catalogues provide a menu of options and service levels.

3. DOC ID
3
Key drivers for Database as a Service
Integration of the two
Wholesale and Retail IT
infrastructure departments
Started in October 2016
• Retail IT Infra
• Wholesale IT Infra
• Split the DBA’s across Delivery and
Consume (SysDBA / AppDBA)
Program Public Cloud
Started in 2017
• We are slow starters and highly
regulated (Global presence)
• Focus on Public cloud
• First SaaS, then PaaS and finally
IaaS

4. DOC ID
4
Provide EnterpriseDB service as an alternative to current RDBMS services (on premise).
• EnterpriseDB / PostgreSQL will be the alternative relational Open Source Database as
planned in the Service Development Plan.
• In the integrated organization it is selected as an additional product.
• This project will introduce EnterpriseDB as the first managed database service
(DBaaS).
• PostgreSQL is already in use at Rabobank Wholesale on a limited scale.
• EnterpriseDB is part of the Database Target Architecture.
• EnterpriseDB is compatible with Oracle PL/SQL, packages & procedures and is a leader
in the Gartner Magic Quadrant for RDBMS.
Background

5. DOC ID
5
What is different in this approach for Rabobank-> Database
as a Services
EnterpriseDB is being offered as a Database-as-a-Service, requiring minimal effort
from Database Service Delivery department, offering maximum automation and
self service
Automatically deploy single cluster or high available stacks CI/CD principles
applied. (Full stack ordering i.e. DB, VM, storage and monitoring)
Enable the DevOps teams to support their applications independently of IT staff.

6. DOC ID
6
Goals for Database as a Service (DBaaS)
§ High availability – near zero planned downtime
§ A self-service computing environment
§ offering the ability to create, consume and pay for database services
§ Improve time to market - Minutes instead of days
§ First time right
§ Service catalogues provide a menu of options and service levels
§ AppsDBA v/s SysDBA
DBaaS for Delivery and Consume
SysDBA
AppsDBA

7. DOC ID
7
Project Milestones
Release Train for EnterpriseDB implementation
Release 0.5 Base
Available as sandbox for testing
Release 0.7 Migration Oracle to EnterpriseDB
High Availability up to A=3D
User Management
Backup/Restore
Monitoring
Automatically create/remove databases,
Crash & planned database recovery
Cloning
RACI
Automated upgrades
Release 1.0 Production Ready
Production Release, including 7 other Risk Applications migrated
Full Self Services (upgrading, capacity management, scale out, user management)
All ITIL processes in place (Incident/Problem/Change), uCMDB, LCM
Release 1.1
IT InfraShop
Offering AIC=322
Security Baseline approved for AIC=322, AIC=333 design available
High Available setup deployable fully automated, offering a high available database setup in 30 minutes instead of two weeks
AIC rating=Availability, Integrity and Confidentiality (1=low, 2=medium, 3= high)

8. DOC ID
8
Questions & Answers