Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The architecture of SkySQL

70 views

Published on

SkySQL implements a groundbreaking, state-of-the-art architecture based on Kubernetes and ServiceNow, and with a strong emphasis on cloud security – using compartmentalization and indirect access to secure and protect customer databases.

In this session, we’ll walk through the architecture of SkySQL and discuss how MariaDB leverages an advanced Kubernetes operator and powerful ServiceNow configuration/workflow management to deploy and manage databases on cloud infrastructure.

Published in: Data & Analytics
  • Be the first to comment

The architecture of SkySQL

  1. 1. SkySQL Architecture OpenWorks May 2020
  2. 2. Agenda ● Quick Background ● Guiding Principles ● High Level Architecture ● Examples of a topology deployment ● Security and Resiliency ● Q&A
  3. 3. WHAT IS SKYSQL? ● Cloud database-as-a-service (DBaaS) for MariaDB Platform ● For transactional (OLTP), analytical (OLAP) and hybrid (HTAP) workloads ● Built and operated by MariaDB Corporation ● Designed to support multi and hybrid cloud deployments
  4. 4. Guiding principles of the architecture ● Flexible ○ Cloud agnostic ○ Kubernetes first ○ Generic Platform for multiple workloads ● Supportable ○ Multi level Monitoring ○ Workload Analysis with Deep Learning ○ Global Operations Team ● Secure ○ Top notch security that is continuously updated ○ Leverage existing cloud services
  5. 5. ServiceNow GCP | AWS | Azure SkySQL operations Jump server Monitoring server Job server SkySQL databases Jump server Kubernetes cluster Database Database Database Commands Metrics SkySQL portal Web UI Inventory Workflows Jobs MariaDB SkyDBAs Customer applications Customer Admins Ident proxy Firewall
  6. 6. Cloud Provider Typical Cloud topology Regions Zones Zonal Level Services Regional Level Services Cloud Level Services
  7. 7. Region Zone 1 Transactions (replica 1) InnoDB Block Store Zone 2 Transactions (replica 2) InnoDB Zone 3 Transactions (replica n) InnoDB MariaDB MaxScale Service (any zone) Block Store Block Store Object Store
  8. 8. Region Zone 1 Transactions (replica 1) InnoDB Block Store Zone 2 Zone 3 MariaDB MaxScale Service (any zone) Block Store Block Store Object Store Analytics (replica 1) Column Store Transactions (replica 2) InnoDB Analytics (replica 2) Column Store Transactions (replica n) InnoDB Analytics (replica n) Column Store
  9. 9. Typical Deployment Flow ● I want ● Master Slave topology with 2 slaves ● Use “4CPU 15Gig RAM, 1TB Disk” SkySQL UI ● Here you go ● Connect String
  10. 10. High Level Deployment Flow ● Store topology as a customer record in SNOW ● Kickoff deployment workflow ● Start Kubernetes cluster ● Create the deployment sets ● Launch management and product containers ● Operator controls the launch sequence of product and then continuously monitors it ● Sanity Test the deployment ● Send confirmation email to customer
  11. 11. ● Leverage IaaS providers ○ HA, Encrypted Storage, Firewalls, Hardened OS images, continuous patching ● Leverage Backend workflow automation and UI ○ ServiceNow is a proven and stable platform for WFA ○ Secure front end UI is a SNOW application ● Additional steps on SkySQL ○ Whitelisting of IP addresses ○ LDAP and Google Auth support ● MariaDB operator is the overseer for any alerts/mishaps ○ Watches each container for anomalies ○ Takes corrective action to fix issues ● Insights using Deep Learning ○ Help customer predict and prepare for heavy loads Security and Resiliency
  12. 12. Thank you! Questions?

×