You can’t have cloud-native applications without a modern approach to databases and backing services. Data professionals are looking for ways to transform how databases are provisioned and managed.
In this webinar, we’ll cover practical strategies you can employ to deliver improved business agility at the data layer. We’ll discuss the impact that microservices are having in the enterprise, and what this means for MySQL and other popular databases. Join us and learn the answers to these common questions:
● How can you meet the operational challenge of scaling the number of MySQL database instances and managing the fleet?
● Adding to this scale challenge, how can your MySQL instances maintain availability in a world where the underlying IT infrastructure is ephemeral?
● How can you secure data in motion?
● How can you enable self-service while maintaining control and governance?
We’ll cover these topics and share how enterprises like yours are delivering greater outcomes with our Pivotal Platform managed MySQL.
Now you can scale without fear of failure.
Presenters:
Judy Wang, Product Management
Jagdish Mirani, Product Marketing
2. Pivotal’s Database Offerings
Operational AnalyticalMixed
Pivotal MySQL Pivotal Postgres Pivotal Greenplum
● High speed - tuned for OLTP
● Web scale
● Simple and easy to set up
● Thriving community of
experts who share best
practices
● Mixed OLTP-OLAP workloads
● Ideal for complex stored procedures
and intricate designs
● Flexibility offered by extensions
● Common target for Oracle migrations
● Massively parallel for analytics
at speed and scale
● Infrastructure-agnostic from
bare metal to cloud
● Integrate structured and
unstructured data in a single
environment
PCF PKS/on-premPKS/on-prem
3. The Emerging Need for Data Transformation
Your data organization needs a path to be a part of the transformation to cloud
native applications
● Certified DBAs spend wasted time running a ticket queue
● Growth in software practice and business bottlenecked by data/data team
● Developer productivity is hindered by data complexity and interdependence
● Held hostage by enterprise database vendors’ licensing tactics
5. ➔ Developers spend inordinate amounts of
time for provisioning and setting up
databases
➔ Cloud infrastructures are ephemeral
requiring hardened availability at the
software layer
➔ New distributed architectures result in an
explosion of database instances
➔ Operators are overburdened with
configuring, managing, and monitoring
databases
What We’re Hearing
6. Operational
Efficiency
__
Deliver highly
available, resilient,
up-to-date systems at
a lower cost
Developer
Productivity
__
Get apps to market
faster by giving
developers the tools
and methods
Secure By
Default
__
Apps that are easy to
patch and incorporate
best practices
Multi-Cloud
Success
__
Make it possible to
build and run
effectively on any
cloud
Our customers achieve
transformative results at scale
MySQL for PCF enables these outcomes
7. ● Automate provisioning of databases on-demand using the platform,
reducing DBA toil
● Simplify data monoliths into smaller & cheaper database backing
microservices
● Integrate native platform tools & components for streamlined day 2
experience
● Enable secure & sane database defaults with per-instance configurations
to match workload profiles
● Separate from vendor product lock-in, adopt OSS to reduce cost and
leverage community expertise
Value of MySQL for PCF
14. API access makes change management easier
● Define a API that projects a data model to
match the needs of the consuming
microservices
● API is the only permissible access point to a
microservice’s data
● Data API provides a contract for accessing
data
● Allows more flexibility for (and isolation
from) changes to backing stores
20. Tier 3
Tier 2
Tier
0
Tier 1
Non-mission critical
Dev & Test
Everything else
Not used
Enterprise DB solutions
Mission critical workloads
The new fleet of databases requires a new way of thinking
21. Tier 3
Tier 2
Tier
0
Tier 1
Mission critical workloads:
- HA Clusters
- Leader-Follower
Mission critical and shared data sets:
- Leader-Follower
Enterprise DB solutions
- Data Monoliths
Manage a fleet of smaller databases that match your
workload profile
Non-mission critical, Dev & Test:
- Single node
- Leader- Follower
23. Recovery Time Objective In how much time you need to recover your IT infrastructure and services following a disaster in order to maintain business continuity?
Availability topologies
App App App
Recovery Point Objective How much time worth of data loss you can tolerate in the event of a disaster in order to maintain business continuity?
Good Better Best
Good Better Best
24. Recovery Time Objective In how much time you need to recover your IT infrastructure and services following a disaster in order to maintain business continuity?
Complexity & Cost How much time, effort, and technical expertise is required to troubleshoot in the event of a disaster in order to maintain business continuity?
Availability Costs & Benefits
App App App
Recovery Point Objective How much time worth of data loss you can tolerate in the event of a disaster in order to maintain business continuity?
Good Better Best
Good Better Best
Low Medium High
28. Developer creates high
availability instance and
binds it to app
VM dies,
App fails over
BOSH resurrector restores
high availability, App fails
back
Disk
MySQL
Disk
MySQL
Disk
MySQL
App
Jumpbox
Proxy Proxy Proxy
Backups
Disk
MySQL
Disk
MySQL
Disk
MySQL
App
Jumpbox
Proxy Proxy Proxy
Backups
Disk
MySQL
Disk
MySQL
Disk
MySQL
App
Jumpbox
Proxy Proxy Proxy
Backups
HA Clusters - Failover
29. BOSH updates the 1st
node, no impact to
Applications
BOSH continues to
the 2nd, Apps fail
over
BOSH finishes the 3rd
node, Apps fail back
Disk
MySQL
Disk
MySQL
Disk
MySQL
App
Jumpbox
Proxy Proxy Proxy
Backups
Disk
MySQL
Disk
MySQL
Disk
MySQL
App
Jumpbox
Proxy Proxy Proxy
Backups
Disk
MySQL
Disk
MySQL
Disk
MySQL
App
Jumpbox
Proxy Proxy Proxy
Backups
HA Clusters - Rolling Upgrades
30. ● Multi-master: Any node is available for
failover
● Out of sync nodes are automatically evicted
● In Leader-Follower, if one node crashes, the
service is down till manual failover
completes.
BOSH
DNSProxy
MySQL
server
Proxy
MySQL
server
Zone1Zone2Zone3
Proxy
App
MySQL
server
HA Deep Dive - The Cluster
31. MySQL
server
Zone1Zone2Zone3
● Spreading three nodes across multiple AZs
prevents against isolated IaaS failure.
● Worst case: Cluster is down, not split brainBOSH
DNS
Proxy
Proxy
Proxy
App
MySQL
server
MySQL
server
HA Deep Dive - Availability Zones
32. MySQL
server
MySQL
server
MySQL
server
Zone1Zone2Zone3
Proxy
● We control all the traffic to a single master
with proxies providing super-fast failover
times
● Failover is near-immediate when one
node crashes.
● The proxies also help protect from split
brain and from some Galera limitations
Proxy
Proxy
BOSH
DNS
App
HA Deep Dive - Proxies
35. Multi-DC Replication - Preview
Active-Passive App Layer Active-Active
*GSLB = Global Service Load Balancer
Secondary DC Primary DC Secondary DCPrimary DC
GSLB GSLB
App A App A’ App A App A’
failover
failover
failover
38. Enterprise Ready
Scale to Hundreds of DB Instances for Modern Microservices-based Applications
● Customize service plan definitions to support internal chargeback packages and
enforce resource constraints.
● Highly available and resilient to node, availability zone, or site failure (beta). Zero
downtime upgrade and patches
● Automate periodic backups and allow for restoring from a backup
● Data in motion is protected via transport layer security.
● Get visibility into details of service operation through standard monitoring and
logging tools. Receive alerts for faster problem resolution