Sacrifice SQL for an elastic database? Or sacrifice elasticity for a SQL database? Most of today’s database options force you to choose:
+ Easily scale your database and achieve continuous availability in line with today’s modern, often cloud-based architectures, or
+ Preserve transactional consistency, data durability, and a familiar SQL interface - often requirements for applications with business-critical information.
In these slides, we discuss the emergence of the elastic SQL database that forgoes such compromises and delivers a distributed database built for today’s modern applications. We highlight the emerging need for an elastic SQL database and the benefits that can be derived as a result, including:
+ Lowering total cost of ownership
+ Deployment flexibility
+ Improved performance and availability
+ Faster time to market
5. MAJOR DATA & BUSINESS CHALLENGES
Minimize Cost and Risk,
Maximize Return on Investment
Deliver Updates Fast
to Market
Provide Engaging
User Experiences
Ensure Consistent
Performance and Reliability
Keep Sensitive
Data Secure
16. CHALLENGE WHY NuoDB BENEFITSCHALLENGE
Europe’s Largest Software Company, after SAP
+ Migrating a $3B
business to the cloud
+ Consolidating product
portfolio to an
integrated cloud
platform
+ Designed for the cloud
+ Continuous availability
+ Elastic scalability
+ Significant cost savings
over Oracle
+ Data layer becomes
competitive advantage
17. CHALLENGE WHY NuoDB BENEFITSCHALLENGE
UnaVista reconciliation platform: helping clients reduce regulatory risk
+ New EU regulations
driving demand for
financial trading data
analysis beyond SQL
Server capabilities
+ Data volumes growing
10x over 3 years
+ Scale-out SQL database
+ Continuous availability
+ In-memory transaction
engine separated from
durability layer
+ Unlimited elastic
scalability
+ 10x higher performance
+ Operational efficiencies
+ TCO savings
18. End-to-end Asset Finance Software Platform
CHALLENGE
+ Migrating industry-leading
application to SaaS model
+ Lack of cloud offering
inhibiting growth
+ MySQL couldn’t scale far
enough; Oracle licensing
on AWS too expensive
WHY NuoDB
+ Designed for elastic cloud
scalability
+ Continuous availability
with active-active
architecture
+ Maintains transactional
integrity
BENEFITS
+ Strong ROI for Alfa – and
their clients
+ Reduce infrastructure cost
by 90% over Oracle
+ Increase application
availability and minimize
response time
Good afternoon – welcome to our webinar on “top reasons to deploy an elastic sql database”
Intro me & ariff
Introduce the drivers for a new class of operational database – an elastic sql database – and the key reasons you may want to consider
Live Q&A after the presentation – type questions in the question panel and we’ll get to them at the end
Get started
Software market has fundamentally changed
Whether you are an ISV or an SDO, expectations are no longer that you simply develop and deliver high quality software
It is now about the entire experience
Enterprises used to be responsible for running and managing the software – providing security, uptime guarantees, and ensure consistent performance
Now that responsibility has fallen on the application developer
Rather than simply being a development team – ISVs are now service organizations and must ensure they deliver amazing experiences
And this change is not an easy one – with a world that is more global, mobile, social and data-driven, software development teams have to adapt – or die
In a recent study, market research firm IDC predicted that by 202 30% of software vendors will fail to make the shift to the new service-based reality
Those software organizations who fail will simply not be able to reach new markets, respond to shifting customer demands, and stay competitive
To accomplish this shift, software organizations are rethinking everything about their computing environments - infrastructure, application development and operations – and their business terms
Data workloads are growing – everywhere – and storage and access for large datasets are a growing need as well
Developers are becoming a scare commodity – and the role of developers is changing
Applications are being asked to do more and perform to more demanding requirements …while keeps costs to a minimum
Workloads are being broken down and delivered as collections of loosely coupled services
To accommodate these needs and transform in a service, customer-oriented business software orgs are moving their applications to the cloud
And purchasing patterns and models for licensing software are changing.
As part of this modernization transformation, organizations must also consider how cloud applications will handle and store data
But moving to the cloud is not as simply as just running your existing application on a cloud provider.
Software companies embracing this journey are facing significant data modernization challenges including:
ensuring that workloads are handled responsively, and data is accurate and kept secure
planning and resourcing for handling transactional workloads at scale and under dynamic loading
While Delivering new software and updates to market quickly, maximizing return on investments in database resources, infrastructure, skillsets, and existing application code while minimizing risk and costs.
In addition to the web and application tiers of a cloud-based software as a service, the database plays a significant role and contributes to your overall success
As you look to appeal to a broader market with your cloud-based offering, the database can either become a significant bottleneck or allow you to quickly support new tiers of customers and a rapidly growing customer base.
The last thing you want to do is be forced to rearchitect your application because your database is holding you back. As one of our customers said, “database divorce is hard” – if you architect your service with the right database technology from the start, you will be able to quickly expand your market reach and support a higher volume of customers
Your choice in database can also give you deployment flexibility
The cloud on-ramp is often not a linear path – with many companies gradually shifting workloads to the cloud, and often replatforming some workloads back on-premises. Picking a database that works across environments – on-prem, private cloud, public cloud – gives you that flexibility and agility to respond to market, business and competitive pressures. Just as companies were loath to succumb to vendor lock-in in the past, most want to avoid the modern version of that being peddled by the major cloud providers.
As you begin offering your products as a service, you have the opportunity to tailor different versions of that application to different market segments – gaining new revenue streams
Again, does your database support this model – or does it burden you with high total cost of ownership that makes going after a commodity market prohibitive?
And as you think about the costs of your database – and its impact on your bottom line – the actual database licensing costs are just one piece
Do you have to rewrite significant aspects of your existing application to accommodate the database? Do you have to retrain your staff – or hire new staff – to move to an unfamiliar database interface or API? Does your database address common service-based requirements of continuous availability and maximize your hardware investments?
Moving to the cloud and a service-oriented architecture gives you the opportunity to fundamentally transform your application strategy, and your business
Don’t underestimate the role that the database plays in this transformation
Our world has moved from the mainframe, to client-server, to distributed computing. Advancements in everything from hardware to processing power, application architectures to development processes… have enabled organizations to take advantage of cloud benefits such as agility, elasticity, and scale-out.
One key element - the database tier - has remained stubbornly unchanged.
However, as the business grows so does the challenge to meet requirements of real-time access to data and handling highly dynamic operational workloads within reasonable resource and budget constraints. Databases can accelerate or constrain your business because your choice of database technology affects everything from downtime to application performance to your ability to scale to the overall return you can achieve with your investments.
The database can be considered the lifeblood of the modern application. If you trust the data, you can trust the application.
To be successful in today’s dynamic world, organizations must modernize their database.
So what’s needed to truly be successful?
Organizations cannot risk everything by starting completely fresh. One of the reasons why databases are so essential to business is because they do some things really, really well. They provide consistency and durability for systems of record. Financial institutions count on databases to perform trusted transactions that the world can trust. When data and transactions are compromised there are huge, devastating consequences.
And everyone knows how to “talk to” and access databases. It’s easy to find developers who know SQL. Much easier than re-training all your developers to learn a completely new and immature system.
The ideal solution? A database that provides trusted ACID guarantees and a familiar interface while providing the flexibility for easy, uncomplicated scale-out.
What are your options for a solution?
Traditional relational databases offer:
A familiar SQL interface
ACID compliance for transactional consistency and durability
But…
Are expensive, time consuming, and complicated to scale
Do not provide the agility and flexibility that modern applications demand
NOSQL databases offer:
Scalability and availability
Straightforward scale out
But…
Require developers to code data management into the application itself
Sacrifice data consistency and durability
Force difficult, complex migrations with costly re-writes for SQL applications to gain scale-out benefits
Other NewSQL databases offer scale out benefits with the familiar SQL interface.
But, each optimizes on specific use cases to modernize existing SQL applications and typically sacrifice key database performance in other ways:
For example:
Cannot achieve true data consistency or durability
Unable to efficiently or concurrently process complex queries
Unable to handle online transaction processing workloads
Cannot scale elastically and requires downtime to provision new resources and accommodate growth
Requires significant changes to the application itself in migration scenarios
Cloud databases offer:
Integration with the cloud IaaS provider
Modern pricing models (e.g. consumption)
But…
Are based on traditional relational database architectures not originally designed for scale out and distribution.
Are not hybrid cloud solutions and force lock-in to the cloud environment
CREATE MARKET SLIDE THAT HAS OPERATIONAL, ANALYTICAL, IOT., HTAP, STREAMING…….AND NUODB VERSUS OTHERS
NuoDB appears as a single, logical, SQL database to the application, allowing developers to focus on building great applications, versus dealing with scale-out complexities. Under the hood, NuoDB has a peer-to-peer, two-layer, distributed architecture that can be deployed across multiple data centers and is optimized for in-memory speeds, continuous availability, and elastic scale-out.
The transaction layer consists of in-memory process nodes called transaction engines (TE). Transaction engines handle requests from applications, caches data for fast access, and coordinate transactions with other process nodes in both the transaction and storage layers. As an application makes requests of NuoDB, the transaction engines will naturally build in-memory caches with affinity for that application’s data, allowing NuoDB to maintain high performance.
Handles application requests
Data caching
Coordinates transactions with other process nodes
The storage layer consists of process nodes called storage managers (SM). The storage manager ensures durability of data by writing it to disk, manages data on disk, handles requests from transaction engines (TEs), and sends asynchronous messages to other SMs to commit data to disk and to maintain copies of data in memory. These process nodes provide ACID-guarantees, data redundancy, and data persistence.
Manages writes to disk, ACID-guarantees, redundancy, persistence
Handles transaction layer requests
Coordinates with other storage process nodes
Within both layers, NuoDB can elastically scale out (and back) without any interruption to application service, simply by adding and removing TEs and SMs. This means developers can design applications to access a single logical database and not worry about handling scale out complexity related to dynamic operational workloads. Database operators can scale out the database to accommodate dynamic workloads and not worry about adverse consequences to the application. The result is that developers and operations can focus on truly maximizing performance of both the application and the database.
Layers scale independently
Straightforward ANSI SQL interface
Flexible configuration
Deploy across data centers
Survive failures and perform rolling upgrades
So this is NuoDB – the Elastic SQL database
(slide)
Before we wrap up and take the questions that I see coming in via the question panel, let me just highlight a couple customer examples
Dassault Systemes is a $3b software company, providing manufacturing software solutions – such as CAD/CAM and PLM – to the world’s leading manufacturing organizations around the world.
As with many software markets, theirs is transitioning to the cloud. While a majority of PLM users today still use on-premises solutions, Dassault recognizes that the future is different. The future is cloud based, it is service-based, and it is about integrating their product portfolio into an integrated suite of services they call the 3D Experience where the data tier becomes a competitive advantage.
Dassault has been working with NuoDB for several years and has deployed NuoDB as the relational database back-end to their 3D Experience cloud offering. They selected NuoDB due to the Elastic SQL properties we described in this presentation. Their applications were designed for a relational database back-end – thus maintaining a SQL interface and the traditional relational database properties was important. But unlike traditional relational databases, NuoDB is designed for the cloud and can be easily scaled-out as demands increase.
A second example is the London Stock Exchange and their UnaVista division. UnaVista develops and markets a trade reconcilliation platform that helps LSE and its clients reduce regulatory risk and ensure compliance with stricter regulations. With financial regulatory changes set to take effect in Europe in 2018 – notably the shift from the “markets in financial instruments directive” – or MiFID – becoming a regulation – or MiFIR, UnaVista needed a platform that more easily scale out to accommodate increasing demand and anticipated data volumes.
Their existing database solution could not easily scale out to address this need, but UnaVista didn’t want to abandon the SQL interface and database consistency and capabilities they had come to rely on. They cannot afford any application downtime, and they particularly liked the separate of transaction processing from storage that Ariff described – giving them deployment flexibility and elasticity. Overall they are experiencing significantly higher performance and throughput with NuoDB, while significantly reducing their overall costs.
The final example is Alfa Systems. I had the pleasure of sitting down with Tim Gage a couple weeks ago to discuss their move to the cloud – and I encourage you to watch that interview if you want more details.
Alfa is a leading asset finance software platform, serving some of the largest asset finance organizations – from Mercedes-Benz Financial Services to Toyota Financial Services to Siemens Financial Services and the Commonwealth Bank of Australia. Like many software providers they have traditionally offered their product as an on-premises application but are increasingly seeing demand for cloud-based offerings. As they move to the cloud they sought an offering that they could easily migrate their existing SQL-based applications to and gain new cloud-deployment efficiencies.
They downloaded the free NuoDB Community Edition and had migrated their existing application on their own in just two weeks. The community edition is a fully-functional, freely available version of NuoDB that hundreds of organizations have built and deployed applications with. As those companies look to scale their applications out to handle higher volumes or have storage redundancy, they upgrade to the Professional or Enterprise version of NuoDB – which Alfa has done. Overall Alfa believes that NuoDB will provide significant cost savings over traditional database offerings – value that both Alfa and their end clients will benefit from – and allow Alfa to more easily and seamlessly move to a modern cloud deployment model.
Final slide on NuoDB, the company. We’ve been around for about 7 years pioneering, developing and commercializing this new generation of operational databases – the Elastic SQL database. Hundreds of companies have benefited from our patented, novel approach that brings together the best of both worlds – the traditional relational database reliability and guarantees with the modern cloud flexibility.
With that, we’ll open it up for questions…