Upload
nuodb
View
366
Download
1
Embed Size (px)
Citation preview
KEY DATABASE CRITERIA FOR CLOUD APPLICATIONS+ Matt Aslett, Research Director, Data Platforms and
Analytics
+ Ariff Kassam, Vice President, Product
Copyright (C) 2016 451 Research LLC2
451 Research is a leading IT research & advisory company
Founded in 2000300+ employees, including over 120 analysts
2,000+ clients: Technology & Service providers, corporate advisory, finance, professional services, and IT decision makers50,000+ IT professionals, business users and consumers in our research communityOver 52 million data points published each quarter and 4,500+ reports published each year
3,000+ technology & service providers under coverage
451 Research and its sister company, Uptime Institute, are the two divisions of The 451 Group
Headquartered in New York City, with offices in London, Boston, San Francisco, Washington DC, Mexico, Costa Rica, Brazil, Spain, UAE, Russia, Taiwan, Singapore and Malaysia
Research & Data
Advisory
Events
Go 2 Market
Copyright (C) 2016 451 Research LLC3
A combination of research & data is delivered across fifteen channels aligned to the prevailing topics and technologies of digital infrastructure… from the datacenter core to the mobile edge.
Copyright (C) 2016 451 Research LLC
• Cloud computing has had a significant role to play in driving down the cost of storing and processing data, along with delivering additional benefits such as:• developer and business agility• faster time to adoption for emerging technologies• high availability• reduced infrastructure configuration and management overheads.
• Cloud applications require a database that is able to deliver on the flexibility and scalability advantages of the cloud, while maintaining the resiliency and functionality expected of traditional databases.
4
Databases and the cloud
Copyright (C) 2016 451 Research LLC5
Databases and the cloud
Databases on the cloud
• 2008 – Operational databases on IaaS
• 2009 – Analytic databases on IaaS
• Existing relational database products configured to run on the cloud.
Database-as-a-service
• The on-demand delivery of database management software, consumed by end users as a service.
• In the very early stages of adoption, with most data-related workloads deployed on-premises.
Copyright (C) 2016 451 Research LLC6
DBaaS Adoption TrendsSource: 451 Research Market Monitor
2015 2016 2017 2018 2019 202005000
10000150002000025000300003500040000450005000055000
$ in
M48% CAGR expected for
Operational DBaaS
13%CAGR expected for Operational databases
Operational databases
Copyright (C) 2016 451 Research LLC7
Databases and the cloud
Databases for cloud applications
• A database designed to take advantage of and enable elastic, distributed architecture that supports SaaS applications.
• May or may not run in a public cloud.
Databases on the cloud
• 2008 – Operational databases on IaaS
• 2009 – Analytic databases on IaaS
• Existing relational database products configured to run on the cloud.
Database-as-a-service
• The on-demand delivery of database management software, consumed by end users as a service.
• In the very early stages of adoption, with most data-related workloads deployed on-premises.
Copyright (C) 2016 451 Research LLC
Phases of cloud adoption
8
• Hybrid is not a trend, it’s reality
Copyright (C) 2016 451 Research LLC
Requirement drivers
Social
MobileApplication
Global
Interactive
Local
9
Copyright (C) 2016 451 Research LLC
Requirement drivers
SQL
SchemalessDeveloper
APIs
REST
Flexible
10
Copyright (C) 2016 451 Research LLC
Requirement drivers
11
Distributed
ScalableArchitecture
Virtual
Containers
Elastic
Copyright (C) 2016 451 Research LLC
Limitations of traditional databases• Enterprise architectures have shifted from a scale-up to a scale-out
approach to make use of distributed hardware.• Greater scalability demands• Predictable performance problems
• Traditional relational databases were never designed to cope with modern application requirements• Geographic distribution• Proliferation of cloud• Multiple data types
• Modern application requirements require a rethink of the relational database model 12
Copyright (C) 2016 451 Research LLC
Key Database Criteria for Cloud Applications
13
Scale-out across low-cost distributed commodity architecture
Provision rapidly and scale up and down in response to changing requirements
Always available, actively in multiple locations and regions
Easily monitored, managed and integrated with other applications and services
SCALEABLE DYNAMIC RESILIANT SIMPLE
Copyright (C) 2016 451 Research LLC
Key Database Criteria for Cloud Applications
14
Public, private, hybrid cloud.
Combined operational and analyticprocessing
Able to support high performance workloads, as required
Supports security and access technologies and standards
Support for existing skills and tools (e.g. SQL)
Consistent (tunable if required)
HYBRID PERFORMANT SECURE PREDICTABLE
Copyright (C) 2016 451 Research LLC
• Growing adoption of Databases on the Cloud and DBaaS, but hybrid is not a trend, it’s reality
• Traditional relational databases were never designed to cope with modern application requirements.
• Cloud applications require a database that is able to take advantage of and enable elastic, distributed architecture.
• While also maintaining the performance, resiliency, security and functionality expected of traditional databases.
Conclusions
15
Copyright (C) 2016 451 Research LLC
Thank [email protected]@maslettwww.451research.com
The Elastic SQL Database for Applications in the Cloud
NUODBMay 2, 2023
DATABASE FOR CLOUD APPLICATIONS
18
Virtualization, Commodity & Cloud Scale out / in ACID
(consistency)Existing SQLskills & code
SQL database abstraction
What everyone wants:
What they don’t want to lose
“Elasticity” “SQL”
“I want to elastically scale my SQL RDBMS to the cloud”
ContinuousAvailability
NuoDB combines the scale-out simplicity, elasticity, and continuous availability that cloud applicationsrequire with the transactional consistency and durability that databases of record demand.
AgilityRespond to market changes faster:+ Dynamically add or remove
servers+ Deploy on public cloud,
private cloud or on-premises
+ Modify applications faster with a consistent SQL API
Total Cost of OwnershipReduce overall costs:+ Lower database licensing
costs+ Better server utilization+ Reuse existing SQL code
and skillsets+ Provision servers with
demand – no pre-provisioning
Time to MarketBring applications to market faster:+ Reuse existing SQL logic
and skills+ Trust the database for data
management logic
Customer SatisfactionImprove application experience:+ Zero downtime
(including server outages& rolling upgrades)
+ Consistently better performance
+ Automated redundancy and disaster recovery
THE ELASTIC SQL DATABASE
NuoDB+ Founded in 2010+ Management team and investors
are database pioneers+ Patented elastic SQL database+ Leading SaaS & on-premises
applications run on NuoDB+ HQ in Cambridge, MA
20
Copyright © 2016 NuoDB
KEY IDEA #1: DISTRIBUTED BY DESIGN
21
1. Start with a client-server DBMS2. Try to turn it into a Distributed
System
1. Start with a Distributed System2. Deliver database services on this
system
DON’T DO
A single logical database that scales elastically
Compromise database or application to achieve scale-out
22KEY IDEA #2: SEPARATION OF DUTIES
Separate transactions from storage
One logical database+ Both tiers survive failures and rolling upgrades at any peer
+ Allocate servers and server types based on workload
Transactions in memory+ Working data set in memory + No shards / explicit partitioning+ Scale throughput & clients
on-demand+ Transparent to applications
Storage is redundant & flexible+ Durable persistence+ Automatically replicate to
multiple locations+ Tunable consistency models
TETE TE
SM SM
NuoDB ARCHITECTURE IN PRACTICE
Nuo
DB d
atab
ase
App App App
+ Fully redundant+ Elastically scalable+ Continuously available
Available host
SM Storage Manager (SM)
Transaction Engine (TE)TE
Scale-out adds
+ Active/Active across single DC or multiple AZ’s
TYPICAL DEPLOYMENT SCENARIOS
24
Copyright © 2016 NuoDB − NuoDB Confidential
Fully Redundant … with snapshot mgmt Scale-Out
Snapshots
Running NuoDB on four hosts (2 TEs and 2 SMs) provides a fully redundant deployment of NuoDB that can survive
any host failing.
Running NuoDB on five hosts (2 TEs and 3 SMs) provides a fully redundant deployment of
NuoDB that can survive any host failing, and provides for snapshot mgmt.
…
…
To increase throughput, simply add TEs/SMs to other available machines
on demand.
TE – NuoDB Transaction EngineSM – NuoDB Storage Manager Active Engines
TYPICAL DEPLOYMENT SCENARIOS
25
Copyright © 2016 NuoDB − NuoDB Confidential
Disaster Recovery Active-Active(Across Availability Zones)
TE – NuoDB Transaction EngineSM – NuoDB Storage Manager
Primary Site
Disaster Recovery Site
Availability Zone 1
Availability Zone 2
Region 1 Region 2
Region 3
Active-Active-Active(Across Regions)
NoSQL
Traditional RDBMS
DBMS OPTIONS FOR CLOUD 26
“Elasticity”Scaling simplicity, continuous availability
“SQL
”D
urab
ility
, con
sist
ency
, rec
over
abili
ty
NewSQL
Cloud DBMS
“NuoDB was the best database to support
our need for scaling up our distributed network
to meet demand requirements while
maintaining transactional
consistency and integrity.”
Bruce LawlerCo-founder & Chief Product Officer
SUMMARY+ The Elastic SQL database
NuoDB is the only database for scaling your business applications to the cloud
The elasticity of the cloud without sacrificing the benefits of SQL Continuous availability with automated disaster recovery
+ Build your business, reduce your costs Improve customer experience and get to market faster while
lowering your overall application and infrastructure costs
27
Copyright © 2016 NuoDB − NuoDB Confidential
QUESTIONS & ANSWERS
Use the “Questions” box on your GoToWebinar panel to submit your questions
28
Copyright © 2016 NuoDB − NuoDB Confidential
29
The Elastic SQL Database
Thank You For Joining Us