Hardware Virtualization and cloud computing allowed us to increase resource utilization and increase our flexibility to respond to business demand. Docker Containers are the next quantum leap - Are they?! Databases always represented an additional set of challenges unique to running workloads requiring a maximum of I/O, network, CPU resources combined with data locality. In this session we will walk you through characteristics, performance, value, architecture and operations of heavy containers. Additionally, a short live demo to prove the concepts and results will feature a database of 1.2 billion rows of data.

1. Running Databases in Containers.
How to Overcome the Challenges of Data
Prepared for
Frank Stienhans
CTO
Ocean9

2. BARE METAL
Subjective Perspective
June 10, 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 2
Evolution of Enterprise IT
1.More Choices
2.Faster Delivery
3.Higher Density
4.Increased Control
VIRTUALIZATION
CLOUD
CONTAINERS

3. What is it
• Standardized Application Virtualization
• Application defined as Image, without the OS Kernel
• CPU, RAM, Network, Mount & Process Isolation
• Begin: ~ 2006 @ Google
June 10, 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 3
Containers

4. Value
1. Enable quick provisioning and scaling
2. Enable Higher Resource Density
3. Increased Control over workload Placement and Usage
June 10, 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 4
Containers

5. June 10, 2017 5
Adoption Phases
1.
Frontends
2.
Applications
3.
Databases
FRONTEND APPLICATION DATABASE
RISK
Blast Radius Single User Many Users All Users
Recovery Minutes Minutes Hours - Days
BENEFIT Cost Savings $ $$ $$$

6. © Copyright, 2017, Ocean9, Inc., All Rights Reserved
Heavy Containers
“Heavy Containers”
Containers with a lot of State
June 10, 2017 6
Definition

7. © Copyright, 2017, Ocean9, Inc., All Rights Reserved
Heavy Containers
1. Local State – Focus Today
2. Long Life
3. Highest Security
June 10, 2017 7
Challenges

8. Available Resources in
Virtual Machine Instance Type
Traditional Cloud Sizing
June 10, 2017 8
Databases before Containers
• DB Sizing: Function of …
– RAM
– CPU
– Network
– I/O
• DB Utilization
– 5% average utilization is normal
– Hence, 95% waste
DB Resources
Required
for a predicted Peek
CPU
RAM
DB Resources
utilized on Average

9. © Copyright, 2017, Ocean9, Inc., All Rights Reserved
Cloud Native Sizing
June 10, 2017 9
Database with Container
• Fill the DB Host with Apps
(Stateless Containers)
• Grow your DB container as if
those do not exist.
• Keep some resource reserve as
a buffer
Available Resources in
Virtual Machine Instance Type
DB Resources
utilized on Average
App App App App App App
App App App App App App
App App App App App App
CPU
RAM

10. © Copyright, 2017, Ocean9, Inc., All Rights Reserved
Triple Site Database Setup in one GEO Region
June 10, 2017 10
Cloud Native Maximum High Availability
Available Resources in
Virtual Machine Instance Type
DB Site C
Available Resources in
Virtual Machine Instance Type
DB Site A
App App App App App App
App App App App App App
App App App App App App
Sync DB
Replication
Available Resources in
Virtual Machine Instance Type
DB Site B
App App App App App App
App App App App App App
App App App App App App
Sync DB
Replication

11. June 10, 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 11
Network Filesystems for HPC Persistence
DB Host
::
X1.32xlarge
::
Amazon EC2
Network 20G
Your Apps
I/O ~ 10G
AWS
EBS
Ephemeral
Locally Attached
SSD
DB Replication
Data Integration
Network / Cluster
File System for
Tier 1 I/O
Max Max

12. June 10, 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 12
Amazon EC2 R4 Family
x x x x
x xx x
x x x x
x x x x
16 X-large
• RAM : 488 GB
• CPU : 64 vCPUs
• Network : 20 Gbps
• EBS I/O :~ 10 Gbps
X-large
• RAM : 30 GB RAM
• CPU : 4 vCPUs
• Network : ~ 1.25 Gbps
• EBS I/O : ~ 0.60 Gbps

13. June 10, 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 13
Azure, same answer
DB Host
::
Azure
Virtual Machine
Network 25G
Your Apps
I/O ~ 10G
Azure
Premium
Disks
“Resource Disk”
Locally Attached
SSD
DB Replication
Data Integration
Network / Cluster
File System for
Tier 1 I/O
Max Max

14. Heavy Containers
1. Intelligent Placement (4D : CPU, RAM, Net, I/O)
2. Real-time Monitoring
3. Data Agility and Data Performance (usually XOR)
4. Density
June 10, 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 14
Needs

15. Heavy Containers
1. Running Virtual Machine
2. No Storage
Linux Bash
>> ray docker recover hana2/206
Example uses SUSE Linux 12 SP2 and SAP HANA SPS 12
Demo

16. June 10, 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 16
Output:
SAP HANA
System
with
1.2 billion
rows
Storage
Docker Image
Docker Container

17. One Click Away
June 10, 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 17
Inbuilt Automated Fallback
HANA
Production
HANA
Production
Container Virtual Machine
Backup & Recovery
OR
Synchronous
DB Replication

18. Born in the Cloud SAP-as-a-Service
June 10, 2017 © Copyright, 2017, Ocean9, Inc., All Rights Reserved 18
The Ocean9 Solution
Enterprise Class
• High performance
• High availability
• Strict security
PLUS
• Cloud native capabilities
• Database containers
Ocean9 Intelligent Platform
Database-as-a-Service Business Apps-as-a-Service
B1on

19. Constantly Growing
June 10, 2017 © Copyright, 2017, Ocean9, Inc., All Rights Reserved 19
Partner Ecosystem

20. Please Meet Us at our Booth #234
June 10, 2017 © Copyright, 2017, Ocean9, Inc., All Rights Reserved 20
Thank You
Attend our Sessions
• Running Databases in Containers. How
to Overcome the Challenges
Frank Stienhans, CTO Ocean9
Wed, June 7th, 8:30 – 9:05 am
• The “known unknown" of Big Data in IoT
Swen Conrad, CEO Ocean9
Wed, June 7th, 5:00 – 5:35 am
Booth #234
Visit us!
Try Ocean9
Born-in-the-Cloud
solutions for SAP

21. Thank you
6/10/2017 21
Frank Stienhans
frank@ocean9.io