How to Manage Scale-Out Environments with MariaDB MaxScale
0 likes57 views
MariaDB MaxScale is a database proxy that provides security, scalability, and high availability for MariaDB deployments. It supports load balancing, query routing, and replication topologies to scale database environments without impacting applications. MaxScale includes features like query caching, security rules, and data streaming to integrate databases with big data platforms. It provides a flexible way to configure and manage database operations.
How to Manage Scale-Out Environments with MariaDB MaxScale
- 1. MariaDB MaxScale Maria Luisa Raviol Senior Sales Engineer - MariaDB
- 2. SERVER Enterprise-grade secure, highly available and scalable relational database with a modern, extensible architecture MAXSCALE COLUMNSTORE Next-generation database proxy that manages security, scalability and high availability in scale-out deployments Columnar storage engine for massively parallel distributed query execution and data loading MariaDB Technology
- 3. MariaDB MaxScale Latest GA Version 2.1 Part of MariaDB TX and AX Offering Next Generation Database Proxy for SCALABILITY SECURITY HIGH AVAILABILITY DATA STREAMING
- 4. MariaDB MaxScale Concept DATABASE SERVERS MASTER SLAVES Binlog Cache Insulates client applications from the complexities of backend database cluster Simplify replication from database to other databases CLIENT PROTOCOL SUPPORT AUTHENTICATION DATABASE MONITORING LOAD BALANCING & ROUTING QUERY TRANSFORMATION & LOGGING Flexible, easy to write plug-ins for Generic Core MULTI-THREADED E-POLL BASED STATELESS SHARES THE THREAD POOL
- 5. Read/Write Splitting MariaDB Replication + R/W Split Routing Each application server uses only 1 connection MaxScale monitors the state of each node and only applies operations on available slaves MaxScale creates 2 connections, one for R/W on the master node and one for R/O load balanced on the slave nodes Max Scale R/W Splitting
- 6. Routing based on QUERY TYPES QUERY PATTERNS DATABASE SERVER STATE REPLICATION LAGS Load balancing across database topologies MARIADB MASTER/SLAVE MARIADB GALERA MARIADB MULTI-MASTER AWS AURORA Scaling Scale database environment without application impact Minimize maintenance downtime Connection Based Routing readwrite MASTER SLAVES read write Statement Based Routing (Read- Write Split) readwrite MASTER SLAVES read & write
- 7. MariaDB HA Topology with MaxScale Application / App Server MariaDB MariaDB MariaDB Application / App Server
- 8. MariaDB Cluster Failure Management Galera uses quorum based failure handling ● When cluster partitioning is detected, the majority partition "has quorum" and can continue ● A minority partition cannot commit transactions, but will attempt to re-connect to primary partition ● MaxScale takes care that connections reconnect to available nodes Application / App Server MariaDB MariaDB MariaDB MaxScale
- 9. Scaling: Tunability Route all reads to master subsequent to a write for a configurable amount of time or number of operations Route queries to only those slave that are less than configurable replication lag behind master Route all queries that match a pattern(regex) to specific servers Weighted routing
- 10. Query Cache in memory LRU cache. Clients Database Servers Query Cache Filter CACHE QUERY RESULTS IN MAXSCALE FOR CONFIGURABLE TIMEOUT FOR CACHED QUERIES RETURN RESULTS FROM CACHE Handle large amount of read operations with high performance
- 11. Security in MaxScale Black & White List Connection Rate Limitation End to End SSL Database Firewall Filter for SQL Injection protection Selective Data Masking HIPPA/PCI Compliance Maximum Rows Returned Limit DDoS Protection Transport layer security between applications, proxy & databases DDoS Protection LDAP/GSSAPI Authentication Support
- 12. QUERY FAILED: 1141 ERROR: Required WHERE/HAVING clause is missing rule safe_select deny no_where_clause on_queries select rule safe_cust_select deny regex '.*from.*customers.*' user %app-user@% match all rules safe_cust_select safe_select Security DATABASE FIREWALL FILTER SELECT * FROM CUSTOMERS; MaxScale Database Servers 1 2 3 Database Firewall Filter Allow/Block queries that MATCH A SET OF RULES MATCH RULES FOR SPECIFIED USERS MATCH ON • date/time • a WHERE clause • query type • column match • a wildcard or regular expression or function name Protect against SQL injection Prevent unauthorized data access Prevent data damage
- 13. Operational Use Cases Dynamically configure server, listener, monitor Dynamically configure database firewall rules Query Duplication Query Cache DUPLICATE QUERY BETWEEN PRODUCTION AND STAGING FOR UPGRADE VERIFICATION DUPLICATE QUERY BETWEEN DATABASE AND EXTERNAL APPLICATIONS FOR QUERY ANALYTICS Query logging CLUSTER WIDER QUERY TUNING Query translation TRANSLATE QUERIES SYNTAX FROM ONE PROTOCOL TO ANOTHER ASYNCHRONOUSLY UPGRADE APPLICATIONS AND DATABASE INVOKE EXTERNAL OPERATIONAL TOOLS FOR SERVER DOWN/UP EVENT MANAGEMENT MANAGE FAILOVER - PROMOTE SLAVE TO MASTER UPON FAILURE
- 14. Binlog conversion to Avro Streaming of Change Data Capture events (binlog) to big data environments Data Streaming Change Data Capture Clients EMR MariaDB ColumnStore Big Data Platforms AVRO or JSON events Streaming MariaDB Master Binlog to AVRO conversion
- 15. Thank you