Meeting the Demands of Today's Digital Business
•Download as PPTX, PDF•
1 like•140 views
The document discusses the need for a modern data tier to support digital businesses and consumer-grade applications. It outlines how traditional enterprise applications often go down or are slow, and are difficult to scale. A new approach using database load balancing software is presented, which allows unlocking the power of modern databases without code changes. Key benefits include high availability, performance, and ability to scale anywhere. It provides examples of how the load balancing solution enables zero downtime for maintenance and unplanned outages, improves performance, and allows cross-cloud and hybrid deployments. Customer case studies demonstrate benefits like cost savings, revenue increases, and avoiding development time.
Recommended
Recommended
More Related Content
What's hot
What's hot (7)
Similar to Meeting the Demands of Today's Digital Business
Similar to Meeting the Demands of Today's Digital Business (20)
Recently uploaded
Recently uploaded (20)
Meeting the Demands of Today's Digital Business
- 1. ©2016 ScaleArc. All Rights Reserved. 1 Meeting the Demands of Today’s Digital Business The need for a modern data tier
- 2. ©2016 ScaleArc. All Rights Reserved. 2 Today’s Consumer Apps Have Redefined our Expectations Never down Always fast Scale anywhere
- 3. ©2016 ScaleArc. All Rights Reserved. 3 Enterprise-grade Apps Don’t Meet Digital Business Needs • They go down – The business loses revenue, and you get woken up • They’re slow – The business loses customers, and you get yelled at • They’re hard to scale – The business can’t grow, and you miss your MBOs Consumer Grade is the new Enterprise Grade
- 4. ©2016 ScaleArc. All Rights Reserved. 4 What’s Holding You Back? The Data Tier The database hiccups, and your apps throw up • Database failover takes down the app • Maintenance takes down the app • Scaling takes code changes • And the cloud just makes it worse
- 5. ©2016 ScaleArc. All Rights Reserved. 5 You Need a Modern Data Tier – But Your Apps Can’t Use It • A new approach: Database load balancing software • Unlock the power of modern databases without writing a single line of code • Never down • Always fast • Scale anywhere Transparent deployment – no code changes to the app or database
- 6. ©2016 ScaleArc. All Rights Reserved. 6 PrimaryPrimary SecondaryPrimary replication Avoid Downtime during Unplanned Outages Secondary
- 7. ©2016 ScaleArc. All Rights Reserved. 7 PrimaryPrimary SecondaryPrimary replication Avoid Downtime during Unplanned Outages Secondary 1 ScaleArc performs read/write split
- 8. ©2016 ScaleArc. All Rights Reserved. 8 PrimaryPrimary SecondaryPrimary replication Avoid Downtime during Unplanned Outages Secondary 1 ScaleArc performs read/write split R RR WR W R R W
- 9. ©2016 ScaleArc. All Rights Reserved. 9 Primary Secondary replication Avoid Downtime during Unplanned Outages Secondary 1 ScaleArc performs read/write split R WR W R R W 2 Upon database failure, ScaleArc queues writes W W
- 10. ©2016 ScaleArc. All Rights Reserved. 10 Primary Secondary replication Avoid Downtime during Unplanned Outages Secondary 1 ScaleArc performs read/write split R WR W R R 2 Upon database failure, ScaleArc queues writes 3 After secondary is promoted, ScaleArc directs queries to new primary server Primary W W W
- 11. ©2016 ScaleArc. All Rights Reserved. 11 Primary Secondary replication Avoid Downtime during Unplanned Outages Secondary 1 ScaleArc performs read/write split R WR W R R 2 Upon database failure, ScaleArc queues writes 3 After secondary is promoted, ScaleArc directs queries to new primary server Primary W W W 4 Apps see delay, but do not restart
- 12. ©2016 ScaleArc. All Rights Reserved. 12 SecondarySecondary replication Enable Zero Downtime Maintenance SecondaryPrimary WRRWR R W W R R
- 13. ©2016 ScaleArc. All Rights Reserved. 13 Secondary replication Enable Zero Downtime Maintenance Secondary 1 Mark a database to be taken offline Primary WRRWR R W W R R
- 14. ©2016 ScaleArc. All Rights Reserved. 14 Secondary replication Enable Zero Downtime Maintenance Secondary 1 Mark a database to be taken offline Primary WRRWR R W W R 2 ScaleArc automatically reroutes queries away from offline server
- 15. ©2016 ScaleArc. All Rights Reserved. 15 Secondary replication Enable Zero Downtime Maintenance Secondary 1 Mark a database to be taken offline Primary WRRWR R W W R 2 ScaleArc automatically reroutes queries away from offline server 3 Patch the server and bring it back online
- 16. ©2016 ScaleArc. All Rights Reserved. 16 SecondarySecondary replication Enable Zero Downtime Maintenance SecondaryPrimary WRRWR R W W R R 4 After health check, ScaleArc auto restores traffic to updated server 3 Patch the server and bring it back online 2 ScaleArc automatically reroutes queries away from offline server 1 Mark a database to be taken offline
- 17. ©2016 ScaleArc. All Rights Reserved. 17 Improve Performance CPU Usage R R W W R
- 18. ©2016 ScaleArc. All Rights Reserved. 18 Improve Performance CPU Usage R R WW R 1 Connection pooling, authentication offload reduce CPU usage
- 19. ©2016 ScaleArc. All Rights Reserved. 19 Improve Performance CPU Usage R R WW R 1 Connection pooling, authentication offload reduce CPU usage 2 App-transparent caching improves response time 10x to 60x
- 20. ©2016 ScaleArc. All Rights Reserved. 20 Enable Cross Geo, Cloud, and Hybrid Deployments 1 ScaleArc performs read/write split and geo-load balance database traffic 2 Best performance achieved by Time To First Byte 3 Active replication lag monitoring; avoids sending traffic to lagging nodes 4 Database auto failover is enabled within and across data centers App Servers App Servers Site A Site B or Cloud Web Load Balancer Web Load Balancer Global Traffic Manager replication R W
- 21. ©2016 ScaleArc. All Rights Reserved. 21 See What You’ve Never Seen Before Agentless Real-time Monitoring • Get database-specific metrics to help eliminate bottlenecks One Central Log for all DBs • So information about a DB is available, even if it isn’t Database Performance Analytics • To help rebalance workloads and plan future purchases
- 22. ©2016 ScaleArc. All Rights Reserved. 22 You Could Try to Build This Yourself • Invest in a modern database to get: – Scale out and replication, automated failover • Rewrite your apps to use the new database • And you still wouldn’t get: – Zero downtime for the app – Fastest app performance – Scale across geos or into the cloud It would cost you a lot – and you still won’t deliver consumer grade apps
- 23. ©2016 ScaleArc. All Rights Reserved. 23 Your Peers Have Made their Apps Consumer Grade with ScaleArc Across a Wide Range of eCommerce and SaaS Apps Content/Media Healthcare Financial Services
- 24. ©2016 ScaleArc. All Rights Reserved. 24 Here’s What it’s Meant to their Business $188K saved in a single outage No outage with database failure $320K saved in a year Dev time avoided $2M higher annual revenue No maintenance windows 2x faster website $3M higher revenue 2x faster app rollout Avoided coding
- 25. ©2016 ScaleArc. All Rights Reserved. 25 Nasdaq – Delivering Zero Downtime “The ScaleArc technology is also totally transparent, to both the apps and databases, so we could deploy it with no code changes. It gives us zero downtime.” --Prasad Parvathaneni, Nasdaq
- 26. ©2016 ScaleArc. All Rights Reserved. 26 ScaleArc – Generating a Lot of Buzz
- 27. ©2016 ScaleArc. All Rights Reserved. 27 Why Customers Choose ScaleArc
- 28. ©2016 ScaleArc. All Rights Reserved. 28 Next Steps: 1. Run a live demo 2. Target a critical app for a Proof of Value (PoV) 3. Perform an assessment of your application environment 4. Run the POV and review results 5. Deliver consumer-grade apps! Additional Resources: How it Works Case Studies ??
Editor's Notes
- DONE Here’s the big change – consumer grade is the new enterprise grade. These consumer apps have totally reset our expections for how an app behaves. These apps are never down, always fast, and scale anywhere This a total reversal – enterprise grade used to be the robust class, but now these apps have raised the bar and set the new gold standard.
- DONE “Enterprise grade” has been the gold standard, but even companies’ most robust apps – their enterprise apps – have downtime, are slow, and are hard to scale. These limits directly translate into business cost – in revenue or reputation. You can lose a deal, or a customer for life. This has been the status quo for so long – we’ve kind of gotten used to it. Problem is, status quo is not enough anymore. Why? People’s expectations have changed.
- DONE There’s a better way [[pretty much read the words on the slide – then click to build]] Our software drops in, transparent to the apps and database – and enables your apps to be never down, always fast, and scale anywhere. We do it for SQL Server, MySQL, and Oracle, and you’re not rewriting your apps.
- ScaleArc allows you to do zero downtime maintenance with no app interruption. Let’s say you have to bring the secondary server down to do a patch for that server. Mark that database server offline in ScaleArc. ScaleArc gracefully bleeds that server of all connections and all workloads going to that server at that point in time. And now all the workload is sent to the primary database server. You can now patch the server or do a database upgrade of the secondary server. Once completed, you can bring the patched server back online. After you do a health check to ensure that the patched server is ready and is capable of accepting workloads, ScaleArc automatically restores traffic to the updated/patched server. This allows you to provide zero downtime maintenance to each and every application in your environment. There’s no additional framework necessary to take advantage of zero downtime maintenance. Additionally, zero downtime maintenance with ScaleArc works for all databases and database versions: MySQL, SQL Server, and Oracle. You do not need Oracle RAC to take advantage of this capability. We can work with Oracle DataGuard and Oracle Golden Gate to perform zero downtime maintenance.
- ScaleArc allows you to do zero downtime maintenance with no app interruption. Let’s say you have to bring the secondary server down to do a patch for that server. Mark that database server offline in ScaleArc. ScaleArc gracefully bleeds that server of all connections and all workloads going to that server at that point in time. And now all the workload is sent to the primary database server. You can now patch the server or do a database upgrade of the secondary server. Once completed, you can bring the patched server back online. After you do a health check to ensure that the patched server is ready and is capable of accepting workloads, ScaleArc automatically restores traffic to the updated/patched server. This allows you to provide zero downtime maintenance to each and every application in your environment. There’s no additional framework necessary to take advantage of zero downtime maintenance. Additionally, zero downtime maintenance with ScaleArc works for all databases and database versions: MySQL, SQL Server, and Oracle. You do not need Oracle RAC to take advantage of this capability. We can work with Oracle DataGuard and Oracle Golden Gate to perform zero downtime maintenance.
- ScaleArc allows you to do zero downtime maintenance with no app interruption. Let’s say you have to bring the secondary server down to do a patch for that server. Mark that database server offline in ScaleArc. ScaleArc gracefully bleeds that server of all connections and all workloads going to that server at that point in time. And now all the workload is sent to the primary database server. You can now patch the server or do a database upgrade of the secondary server. Once completed, you can bring the patched server back online. After you do a health check to ensure that the patched server is ready and is capable of accepting workloads, ScaleArc automatically restores traffic to the updated/patched server. This allows you to provide zero downtime maintenance to each and every application in your environment. There’s no additional framework necessary to take advantage of zero downtime maintenance. Additionally, zero downtime maintenance with ScaleArc works for all databases and database versions: MySQL, SQL Server, and Oracle. You do not need Oracle RAC to take advantage of this capability. We can work with Oracle DataGuard and Oracle Golden Gate to perform zero downtime maintenance.
- ScaleArc allows you to do zero downtime maintenance with no app interruption. Let’s say you have to bring the secondary server down to do a patch for that server. Mark that database server offline in ScaleArc. ScaleArc gracefully bleeds that server of all connections and all workloads going to that server at that point in time. And now all the workload is sent to the primary database server. You can now patch the server or do a database upgrade of the secondary server. Once completed, you can bring the patched server back online. After you do a health check to ensure that the patched server is ready and is capable of accepting workloads, ScaleArc automatically restores traffic to the updated/patched server. This allows you to provide zero downtime maintenance to each and every application in your environment. There’s no additional framework necessary to take advantage of zero downtime maintenance. Additionally, zero downtime maintenance with ScaleArc works for all databases and database versions: MySQL, SQL Server, and Oracle. You do not need Oracle RAC to take advantage of this capability. We can work with Oracle DataGuard and Oracle Golden Gate to perform zero downtime maintenance.
- ScaleArc allows you to do zero downtime maintenance with no app interruption. Let’s say you have to bring the secondary server down to do a patch for that server. Mark that database server offline in ScaleArc. ScaleArc gracefully bleeds that server of all connections and all workloads going to that server at that point in time. And now all the workload is sent to the primary database server. You can now patch the server or do a database upgrade of the secondary server. Once completed, you can bring the patched server back online. After you do a health check to ensure that the patched server is ready and is capable of accepting workloads, ScaleArc automatically restores traffic to the updated/patched server. This allows you to provide zero downtime maintenance to each and every application in your environment. There’s no additional framework necessary to take advantage of zero downtime maintenance. Additionally, zero downtime maintenance with ScaleArc works for all databases and database versions: MySQL, SQL Server, and Oracle. You do not need Oracle RAC to take advantage of this capability. We can work with Oracle DataGuard and Oracle Golden Gate to perform zero downtime maintenance.
- ScaleArc allows you to do zero downtime maintenance with no app interruption. Let’s say you have to bring the secondary server down to do a patch for that server. Mark that database server offline in ScaleArc. ScaleArc gracefully bleeds that server of all connections and all workloads going to that server at that point in time. And now all the workload is sent to the primary database server. You can now patch the server or do a database upgrade of the secondary server. Once completed, you can bring the patched server back online. After you do a health check to ensure that the patched server is ready and is capable of accepting workloads, ScaleArc automatically restores traffic to the updated/patched server. This allows you to provide zero downtime maintenance to each and every application in your environment. There’s no additional framework necessary to take advantage of zero downtime maintenance. Additionally, zero downtime maintenance with ScaleArc works for all databases and database versions: MySQL, SQL Server, and Oracle. You do not need Oracle RAC to take advantage of this capability. We can work with Oracle DataGuard and Oracle Golden Gate to perform zero downtime maintenance.
- ScaleArc allows you to do zero downtime maintenance with no app interruption. Let’s say you have to bring the secondary server down to do a patch for that server. Mark that database server offline in ScaleArc. ScaleArc gracefully bleeds that server of all connections and all workloads going to that server at that point in time. And now all the workload is sent to the primary database server. You can now patch the server or do a database upgrade of the secondary server. Once completed, you can bring the patched server back online. After you do a health check to ensure that the patched server is ready and is capable of accepting workloads, ScaleArc automatically restores traffic to the updated/patched server. This allows you to provide zero downtime maintenance to each and every application in your environment. There’s no additional framework necessary to take advantage of zero downtime maintenance. Additionally, zero downtime maintenance with ScaleArc works for all databases and database versions: MySQL, SQL Server, and Oracle. You do not need Oracle RAC to take advantage of this capability. We can work with Oracle DataGuard and Oracle Golden Gate to perform zero downtime maintenance.
- ScaleArc allows you to do zero downtime maintenance with no app interruption. Let’s say you have to bring the secondary server down to do a patch for that server. Mark that database server offline in ScaleArc. ScaleArc gracefully bleeds that server of all connections and all workloads going to that server at that point in time. And now all the workload is sent to the primary database server. You can now patch the server or do a database upgrade of the secondary server. Once completed, you can bring the patched server back online. After you do a health check to ensure that the patched server is ready and is capable of accepting workloads, ScaleArc automatically restores traffic to the updated/patched server. This allows you to provide zero downtime maintenance to each and every application in your environment. There’s no additional framework necessary to take advantage of zero downtime maintenance. Additionally, zero downtime maintenance with ScaleArc works for all databases and database versions: MySQL, SQL Server, and Oracle. You do not need Oracle RAC to take advantage of this capability. We can work with Oracle DataGuard and Oracle Golden Gate to perform zero downtime maintenance.
- ScaleArc allows you to do zero downtime maintenance with no app interruption. Let’s say you have to bring the secondary server down to do a patch for that server. Mark that database server offline in ScaleArc. ScaleArc gracefully bleeds that server of all connections and all workloads going to that server at that point in time. And now all the workload is sent to the primary database server. You can now patch the server or do a database upgrade of the secondary server. Once completed, you can bring the patched server back online. After you do a health check to ensure that the patched server is ready and is capable of accepting workloads, ScaleArc automatically restores traffic to the updated/patched server. This allows you to provide zero downtime maintenance to each and every application in your environment. There’s no additional framework necessary to take advantage of zero downtime maintenance. Additionally, zero downtime maintenance with ScaleArc works for all databases and database versions: MySQL, SQL Server, and Oracle. You do not need Oracle RAC to take advantage of this capability. We can work with Oracle DataGuard and Oracle Golden Gate to perform zero downtime maintenance.
- ScaleArc allows you to do zero downtime maintenance with no app interruption. Let’s say you have to bring the secondary server down to do a patch for that server. Mark that database server offline in ScaleArc. ScaleArc gracefully bleeds that server of all connections and all workloads going to that server at that point in time. And now all the workload is sent to the primary database server. You can now patch the server or do a database upgrade of the secondary server. Once completed, you can bring the patched server back online. After you do a health check to ensure that the patched server is ready and is capable of accepting workloads, ScaleArc automatically restores traffic to the updated/patched server. This allows you to provide zero downtime maintenance to each and every application in your environment. There’s no additional framework necessary to take advantage of zero downtime maintenance. Additionally, zero downtime maintenance with ScaleArc works for all databases and database versions: MySQL, SQL Server, and Oracle. You do not need Oracle RAC to take advantage of this capability. We can work with Oracle DataGuard and Oracle Golden Gate to perform zero downtime maintenance.
- ScaleArc allows you to do zero downtime maintenance with no app interruption. Let’s say you have to bring the secondary server down to do a patch for that server. Mark that database server offline in ScaleArc. ScaleArc gracefully bleeds that server of all connections and all workloads going to that server at that point in time. And now all the workload is sent to the primary database server. You can now patch the server or do a database upgrade of the secondary server. Once completed, you can bring the patched server back online. After you do a health check to ensure that the patched server is ready and is capable of accepting workloads, ScaleArc automatically restores traffic to the updated/patched server. This allows you to provide zero downtime maintenance to each and every application in your environment. There’s no additional framework necessary to take advantage of zero downtime maintenance. Additionally, zero downtime maintenance with ScaleArc works for all databases and database versions: MySQL, SQL Server, and Oracle. You do not need Oracle RAC to take advantage of this capability. We can work with Oracle DataGuard and Oracle Golden Gate to perform zero downtime maintenance.
- Today, you most likely have all your applications connected to a single database server because your apps are not coded to understand how to work with more than one database server. As a result, your CPU usage on the one server is very high and you have a lot of resource contention issues. At the same time, you have a lot of connection management occurring at the database stack. ScaleArc inserts transparently in between the apps and the database: ScaleArc offloads the authentication from the database server and performs connection pooling, which improves throughput and reduces the CPU usage on the database server. We are showing a little CPU usage savings, but for some customers this is a big deal as the authentication requirements are too big for their database server to handle. Next, we can cache read queries. If it is setup as a cache rule, ScaleArc stores a copy of the response for that query in our cache and serves up that query from cache, which significantly offloads a lot of the queries from the database server. This is a very common feature used by many of our customers. The cache range from large reporting queries to very small metadata queries. An example is a customer that caches simple stock code lookups. Let’s say you are looking up AAPL (Apple). You convert that into a stock code that can fetch stock price, graphs of performance, and all related data. The translation can be captured and stored within ScaleArc. In effect, this removes the need to go back to the database server again and again to fetch the data. Another similar example is caching zip codes. And there’s many more. Another capability we now have is the ability to automatically invalidate the cache based upon incoming transactions and writes. Because database caching today is not configurable, you either turn it on or off, you can’t choose what you want to cache, and you don’t realize how effective the caching was because you don’t have any analytics. With ScaleArc’s caching technology, you can offload as much of the workload from the database as possible without changing anything in the application layer. This is the world’s first transparent database caching technology that allows you to use it in a way that you see fit according to your own rule set. With ScaleArc, you get rich analytics that increases your visibility and increases your security. You can now analyze all the database traffic that is going through ScaleArc in near real-time. You can figure out what type of workload is worth optimizing or what type of workload is worth blocking because it may not be a safe workload.
- Today, you most likely have all your applications connected to a single database server because your apps are not coded to understand how to work with more than one database server. As a result, your CPU usage on the one server is very high and you have a lot of resource contention issues. At the same time, you have a lot of connection management occurring at the database stack. ScaleArc inserts transparently in between the apps and the database: ScaleArc offloads the authentication from the database server and performs connection pooling, which improves throughput and reduces the CPU usage on the database server. We are showing a little CPU usage savings, but for some customers this is a big deal as the authentication requirements are too big for their database server to handle. Next, we can cache read queries. If it is setup as a cache rule, ScaleArc stores a copy of the response for that query in our cache and serves up that query from cache, which significantly offloads a lot of the queries from the database server. This is a very common feature used by many of our customers. The cache range from large reporting queries to very small metadata queries. An example is a customer that caches simple stock code lookups. Let’s say you are looking up AAPL (Apple). You convert that into a stock code that can fetch stock price, graphs of performance, and all related data. The translation can be captured and stored within ScaleArc. In effect, this removes the need to go back to the database server again and again to fetch the data. Another similar example is caching zip codes. And there’s many more. Another capability we now have is the ability to automatically invalidate the cache based upon incoming transactions and writes. Because database caching today is not configurable, you either turn it on or off, you can’t choose what you want to cache, and you don’t realize how effective the caching was because you don’t have any analytics. With ScaleArc’s caching technology, you can offload as much of the workload from the database as possible without changing anything in the application layer. This is the world’s first transparent database caching technology that allows you to use it in a way that you see fit according to your own rule set. With ScaleArc, you get rich analytics that increases your visibility and increases your security. You can now analyze all the database traffic that is going through ScaleArc in near real-time. You can figure out what type of workload is worth optimizing or what type of workload is worth blocking because it may not be a safe workload.
- Today, you most likely have all your applications connected to a single database server because your apps are not coded to understand how to work with more than one database server. As a result, your CPU usage on the one server is very high and you have a lot of resource contention issues. At the same time, you have a lot of connection management occurring at the database stack. ScaleArc inserts transparently in between the apps and the database: ScaleArc offloads the authentication from the database server and performs connection pooling, which improves throughput and reduces the CPU usage on the database server. We are showing a little CPU usage savings, but for some customers this is a big deal as the authentication requirements are too big for their database server to handle. Next, we can cache read queries. If it is setup as a cache rule, ScaleArc stores a copy of the response for that query in our cache and serves up that query from cache, which significantly offloads a lot of the queries from the database server. This is a very common feature used by many of our customers. The cache range from large reporting queries to very small metadata queries. An example is a customer that caches simple stock code lookups. Let’s say you are looking up AAPL (Apple). You convert that into a stock code that can fetch stock price, graphs of performance, and all related data. The translation can be captured and stored within ScaleArc. In effect, this removes the need to go back to the database server again and again to fetch the data. Another similar example is caching zip codes. And there’s many more. Another capability we now have is the ability to automatically invalidate the cache based upon incoming transactions and writes. Because database caching today is not configurable, you either turn it on or off, you can’t choose what you want to cache, and you don’t realize how effective the caching was because you don’t have any analytics. With ScaleArc’s caching technology, you can offload as much of the workload from the database as possible without changing anything in the application layer. This is the world’s first transparent database caching technology that allows you to use it in a way that you see fit according to your own rule set. With ScaleArc, you get rich analytics that increases your visibility and increases your security. You can now analyze all the database traffic that is going through ScaleArc in near real-time. You can figure out what type of workload is worth optimizing or what type of workload is worth blocking because it may not be a safe workload.
- DONE Running two or more data centers in active/active mode means all data centers can serve application traffic at the same time. In addition to enabling continuous app availability, running the additional data center(s) in active mode also delivers increased capacity and better performance. This additional capacity improves the economics of active/active operations, since the systems are delivering throughput vs. sitting idle. Implementing an active/active architecture requires more than just replicating the database from one data center to another; applications themselves must understand the database infrastructure and know details such as which servers are closer when clusters span different data centers. Without this insight into database topology and locality, applications can’t send load optimally. With random load balancing, the application will send as much traffic to the remote data center as the local one, increasing WAN traffic and slowing application performance. The ScaleArc software provides a range of traffic management capabilities, enabling an agile data tier. The software supports four key features that make it possible for organizations to easily adopt and benefit from active/active operations: Automatic support for read/write split Geo-aware load balancing Replication-aware serving of data Auto failover within or between data centers
- ScaleArc is very easy to deploy. Our software can be deployed on bare metal servers as well as standard X86 hypervisors such as VMware, Microsoft Hyper-V, KVM, Zen If you are in the public cloud or thinking of deploying in the public cloud, we are supported and partnered with the major cloud providers such as: AWS, Microsoft Azure, Rackspace etc. ScaleArc can go where you need to go and we can help you get there. Our robust RESTful API enables you to integrate into your existing environment. This is a world-class API – all our product functionality is driven by our API – it’s not an after thought. You can manage, monitor, and control ScaleArc through our API and tie its functions into your existing operations and runbooks.
- How would you try to replicate what those companies have done? You could – you’ve got a smart team. Heck – they’d probably LOVE this kind of science project. But let’s look at what it would take. You’d buy that modern database, for those cool new features. Then you’d have to rewrite your software to use it. And here’s the real catch – you still wouldn’t get all those database features to work for the app itself. You wouldn’t have zero downtime, or the fastest performance, or the ability to scale readily. So it would cost a lot – in money and effort. And it’s this last point – the opportunity cost – that’s a really big deal. Gartner and other industry watchers have been increasingly insistent that to succeed today, IT must focus on what IT can uniquely do. The build vs. buy wars are over – “buy” won. So you buy what you can, build what you must. Keep the “build” tasks focused on stuff that only insiders, with a deep understanding of the business, can do – procure the rest.
- DONE We’re really proud of this customer list. You know these companies, and you use their services, so you’re already using ScaleArc. We sit in front of their most vital apps – the ones that impact revenue or reputation – and we’re giving those apps consumer-grade service.
- DONE [[these are all real data points – details here – for each, explain and then ask the pointed question – line this up to start a ROUGH ROI on the spot]] $40K – a single outage, that lasted only 3 minutes, cost that much – with our software, their customer never saw a blip, and that saved them $40K for that ONE incident. What does it cost you when your database goes down? And how many times a year does it happen? $2M – this customer saw a 9-month ROI, with that revenue increase every year, because they no longer have to take their site down for maintenance. What are you losing every time you take down the app for maintenance? Urgent security patches are coming fast and furious now, across the whole tech stack. How often are you delaying them because you’re afraid of downtime? $3M higher rev – consumer patience, and even your Google ranking, takes a hit when your site is slow. Across multiple sites, we increased web performance 50% to 3x. On its main revenue site, we doubled the performance, which translates into $2M to $4M more in revenue every year – we took an average of $3M. How is your site performance impacting your customers, and your search results? $320K – One of our customers was able to skip months and months of app re-engineering, with a bottom line savings of $320K. What would coding for database scale out cost you? Could you use that money – and that talent – another way? 2x faster – Another customer was able to complete a global site upgrade in 4 months instead of 9, because they could skip the recoding. If you could bring your new apps and services to market faster, what would that mean for your business?
- DONE Gartner recognizes and validates the value of our software – they call this market SQL load balancing. Gartner highlighted ScaleArc as a cool vendor last year – one of only three across the entire database market space. They validated the exact capabilities that are driving the revenue increases and cost savings our customers gain.
- DONE (icons will need to be re-linked) Each use case is linked to a relevant case study in this deck.
- [[get the buy in for next steps – show the value we can add]]