Top 5 Ways to Scale SQL with No New Hardware
•Download as PPTX, PDF•
1 like•244 views
This document discusses 5 ways to scale SQL databases without adding new hardware using database load balancing software. It describes automating read/write splitting, replication-aware load balancing, connection management and surge queuing, real-time analytics, and app-transparent caching. This allows scaling out database infrastructure quickly with no app or database changes, increasing efficiency and sustainability while responding to changing needs.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Top 5 Ways to Scale SQL with No New Hardware
Similar to Top 5 Ways to Scale SQL with No New Hardware (20)
Recently uploaded
Recently uploaded (20)
Top 5 Ways to Scale SQL with No New Hardware
- 1. Top 5 Ways to Scale SQL with No New Hardware Achieve up to 24x performance improvement without any changes to applications or database servers.
- 2. ©2017 ScaleArc. All Rights Reserved. 2 Scaling SQL databases is a major challenge
- 3. ©2017 ScaleArc. All Rights Reserved. 3 High Costs: Requires purchasing new, more powerful server hardware and additional licenses
- 4. ©2017 ScaleArc. All Rights Reserved. 4 High Time Investment: Deploying secondary (slave) servers forces significant app code changes for read/write split
- 5. ©2017 ScaleArc. All Rights Reserved. 5 Brittle Architecture: The 1:1 tie of apps to the database perpetuates instability – every database hiccup makes the app throw up
- 6. ©2017 ScaleArc. All Rights Reserved. 6 App Dependency: Adding caching requires code changes and new business logic in all supported apps
- 7. ©2017 ScaleArc. All Rights Reserved. 7 Top 5 Ways to Scale SQL with No New Hardware • Auto Read/Write Split • Replication-aware Load Balancing • Connection Management and Surge Queuing • Real-time Analytics • App-transparent Caching
- 8. ©2017 ScaleArc. All Rights Reserved. 8 Auto Read/Write Split Automatically identify which queries are reads vs. writes Appropriately distribute queries between the primary (master) server and a pool of secondary (slave) servers No need to add code to applications
- 9. ©2017 ScaleArc. All Rights Reserved. 9 Replication-aware Load Balancing Assure that data being read is current, even from secondary servers Monitor the replication lag between primary and secondary servers – Avoid any server whose replication lag exceeds your threshold for delay
- 10. ©2017 ScaleArc. All Rights Reserved. 10 Connection Management and Surge Queuing Connection offload, pooling, and management Persistent SQL connections to database servers ‘Surge queue’ for traffic peaks – Prevent database server overloads and downtime due to crashes – Prevent connection errors without provisioning extra resources for surge loads
- 11. ©2017 ScaleArc. All Rights Reserved. 11 Real-time Analytics for Tuning Performance-centric view of database traffic, including: – SQL connections – Cache usage – Queries processed by the database servers Generate query patterns to quickly identify queries to cache Find performance bottlenecks and perform audits
- 12. ©2017 ScaleArc. All Rights Reserved. 12 App-transparent Caching In-memory cache serves up responses to frequently executed SQL responses – Accelerates application performance – Reduces load on database servers – Increases the number of transactions an existing server can handle Add or remove caching rules with no app changes
- 13. ©2017 ScaleArc. All Rights Reserved. 13 How can you augment your SQL capabilities, with no app or database changes?
- 14. ©2017 ScaleArc. All Rights Reserved. 14 How can you augment your SQL capabilities, with no app or database changes? Database load balancing software Database load balancing software – paired with your SQL database
- 15. ©2017 ScaleArc. All Rights Reserved. 15 How Database Load Balancing Software Lets You Scale SQL with No New Hardware • Scale out your database infrastructure in as little as an hour • No modifications to applications • No new database hardware or licenses • Increase efficiency and operational sustainability • Respond quickly to changes in your environment • Stay ahead of capacity requirements for future needs
- 16. ©2017 ScaleArc. All Rights Reserved. 16 Top 5 Ways to Scale SQL with No New Hardware Achieve up to 24x performance improvement without any changes to applications or database servers. Want to learn more?
Editor's Notes
- For an application to support read/write split, it must understand how to distinguish which queries are reads and which are writes and then appropriately distribute them between the primary (master) server and a pool of secondary (slave) servers. All writes should be sent to the primary (master) server while reads can be spread across secondary (slave) servers. Database traffic management software automatically identifies which kinds of queries are reads and which are writes and seamlessly redirects reads to secondary (slave) servers while directing all writes and transactions to the primary (master) server. There’s no need to add code to applications. Database traffic management software supports read/write split for both queries and stored procedures.
- When employing read/write split, it’s critical that the data being read from secondary servers is current, and that each server’s replication status is as close to the primary server as possible. Different applications have different consistency requirements. A real-time game may have a consistency requirement of under one second of replication lag, whereas a content management system may tolerate as much as 30 seconds of replication lag. Load balancing can boost application performance and increases uptime so long as secondary (slave) servers are current with the primary (master) server. Consistency is key to making this feature work. Building replication-aware load balancing into an application is exceedingly complex. Database traffic management software monitors the replication lag between primary and secondary servers and uses that information to intelligently distribute SQL queries across secondary servers, sending reads only to servers with current data. In addition, database traffic management software allows you to set up the appropriate replication lag threshold for your application’s data consistency needs.
- The average number of web servers has been increasing significantly even as the number of database servers has remained relatively steady. As a result, the average number of connections on a SQL server has gone up tremendously over the last few years, lowering performance and response times. Consequently, in order to prevent database servers from getting overloaded, many database administrators set the maximum number of SQL connections to a fairly low number; for example, MySQL administrators often enable no more than 1,000 connections to a MySQL server. High numbers of SQL connections originating from web/application servers can bog down a database server or overwhelm and crash it, especially during peak traffic bursts. When an application’s traffic spikes, the number of database connections required to meet that demand exceeds the maximum limit set, which triggers connection errors. Database traffic management software provides connection offload, pooling, and management, including maintaining persistent SQL connections to database servers, reusing them for multiple client connections as needed. Database traffic management software also provides a ‘surge queue’ that can allow for more concurrent client connections than available server connections. Surge queuing prevents database server overloads and downtime due to crashes, enabling organizations to ride out peaks and prevent connection errors without needing to provision extra resources for surge loads.
- Having real-time visibility into SQL traffic is crucial for identifying and troubleshooting performance bottlenecks before they become problems. Database traffic management software provides a complete, non-intrusive picture of all SQL connections, cache usage, and queries processed by the database servers. It also gives a performance-centric view of database traffic – for example, displaying query patterns on a graph that highlights slow and frequent queries. Within 15 minutes, database traffic management software can start generating patterns for analysis, such as the most frequent slow queries, which can be used to quickly identify queries to be cached. Operations staff can also use the analytics data to find performance bottlenecks and perform audits.
- By serving up responses to frequently executed SQL queries, ScaleArc’s in-memory cache accelerates application performance and reduces load on database servers, increasing the number of transactions an existing server can handle. Database traffic management software allows application developers or administrators to add or remove caching rules on the fly in seconds, as traffic dictates, with no application changes. Database traffic management software supports caching of stored procedures, as well as read SQL queries, with simple pattern-based rules automatically generated from analytics data