1. Database As A Service (DBaaS) Michael Messina Senior Managing Consultant, Rolta-AdvizeX mmessina@advizex.commmessina@advizex.com / mike.messina@rolta.commike.messina@rolta.com

2. Introduction Michael Messina Senior Managing Consultant Rolta-AdvizeX, Working with Oracle over 20 years Work With Oracle and MySQL Background includes Performance Tuning, High Availability and Disaster Recovery Oracle Database OCP Oracle RAC Certified Expert Oracle Exadata Implementation Specialist Oracle ACE MMESSINA @ ADVIZEX. COM / MIKE. MESSINA @ ROLTA. COM MMESSINA @ ADVIZEX. COM MIKE. MESSINA @ ROLTA. COM www.tusc.com / www.roltasolutions.com www.tusc.comwww.roltasolutions.com

3. Agenda Cloud Computing Cloud Deployment Model Types Of Cloud Implementations Old Important Buzz Words Roles and Responsibilities What is Database As a Service Components of Database As a Service Advantages of Database As a Service Drawbacks to Database as a Service Common Drivers/Usage of Database As a Service Understand How Database As a Service Impacts You Business Service Level Agreements Types of Outages to Cover in SLA Questions / Discussion

4. Cloud Computing NIST Definition of Cloud Computing “Cloud computing Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.” Ubiquitous: This implies that the resources are available and ready for consumption. Convenient: Make it easy for the consumer to acquiring resources. On Demand:Ability to eliminate the step of converting resource requests into resource approval and acquisition tasks. Shared Pool:The resources are shared, not dedicated, which implies mobility of flexibility in terms of assigning resources. Rapid: Eliminate or shorten the time window between resource request being made and its fulfillment.

5. Types Of Cloud Implementations Infrastructure as a Service (IaaS)  Infrastructure components include ( Storage / Network & Compute capabilities)  Service provider delivers infrastructure as a generic commodity.  Can be a Hosted virtualized environment managed by a provider.  Can be a dedicate hardware environment managed by a provider.  Includes Servers, network  Generic purpose, end user consumes the infrastructure components independently. PaaS – Platform As a Service  IaaS delivering a platform for specific use cases (Databases / Application Servers / Cloud Storage ).  Platform is operated and managed by a external service provider.  End user consumes the platform as a whole. Software as a Service (SaaS) - Hosted Application  The service provider delivers the application over the cloud.  End user consumes the application over the Internet – Mobile Devices / Web based etc.

6. Cloud Deployment Model Private Cloud  Exclusive use for a Single organization  Service over entity private internal network (WAN or LAN)  Security model controls access within the client entity units  Provided to select set of internal entities or set of internal users  Nothing is public domain or shared outside the defined entity that is authorized to use Public Cloud  Service offered to the general public over the internet on shared cloud platforms.  Owned, Controlled and managed by a Cloud Service Provider Community Cloud  Cloud for a specific community of users  Can be owned, operated and managed by multiple organizations Hybrid Cloud  Private Cloud in a public space

7. Old Important Buzzwords Service Level Agreement (SLA)  Contract agreement between service provider and entity or user of services  Defines the level of service provided  Availability  Responsibilities  Priorities  Performance level  Etc. Service Provider / Managed Services Provider / Cloud Provider  Organization providing services to a user or other entity for a fee Managed Services  External Entity that manages services for a user or organization for a fee  Network Managed Services  Database Managed Services  Operating System Managed Services  Software Managed Services

8. Roles & Responsibilities of Cloud Computing Consumer Roles  Power User – Admin for the Consumer  End User – A end user using the services Service Provider Roles & Responsibilities  RACI  R – Responsible  A – Accountable  C – Consulted  I - Informed  By clarifying roles and responsibilities at the very initial stage of the process design, RACI helps setting up the proper expectations. In the cloud this becomes more critical as you have the distinction between internal IT and services from the cloud provider.

9. Roles & Responsibilities of Cloud Computing Security in the Cloud  Three Parts of Cloud Security  Host Security  Network Security  Data/Information Security  Ensure all security requirements are clear and defined.  Compliance PCI, HIPPA, Sarbanes-Oxley Act, etc.  Business Continuity and Data Recovery  Audit Trail / Logs (eDiscovery)  Others Unique to your organizations requirements  Cloud Security Controls  Deterrent Controls  Warning signs that access by unauthorized persons will have serious consequences.  Preventative Controls  Prevent the breach in the first place.  Detection Controls  Detect a security Breach so corrective action can be taken to limit breach  Correction Controls  Limit the Damage, corrective actions in event of security breach

10. Roles & Responsibilities of Cloud Computing Service Level Agreements  Provider should have a Service Catalog  Define service offerings  Availability (RTO, RPO, Protection)  Security (Compliance, Controls)  Capacity (CPU, Memory, Storage, Network)  Performance (KPIs, Monitored, NoKPIs)  Support (hours of availability, maintenance windows)  Define the service levels for each service offering Typical Service Levels  > 99%  > 99.95%  99.999%  Service Credits for missing target service level  > 99% but < 99.95%10% credit  < 99%25% credit

11. Roles & Responsibilities of Cloud Computing Service Level Agreements (SLA’s)  Will define roles and responsibilities between internal IT and Cloud provider and any additional managed services  Contingency/DR Plan  What happens if the primary service goes down is there a backup service?  Define Availability Requirements  What is the Availability and penalties for not meeting availability requirements  Define Performance Requirements  What are the KPIs and levels for those KPIs  Define Security Requirements  What are they and what is used to meet the requirements  Define Capacity and Capacity Management  How do I grow and approval process to grow  Change Management  When is maintenance windows  Change Notifications and Approvals

12. Roles & Responsibilities of Cloud Computing Service Level Agreements (SLA’s)  Incident Management (Event Management)  How do I report an Incident  What is the response time for responding to an incident  How is incident resolution reported backup  How is priority defined for an Incident  Requests Management  How do I make requests  What is the expected response time to requests  How is priority defined to requests  Problem Management  How do I report multiple incident and escalate to a problem?  How is problems report back  How is priority defined

13. Types of Outages You ensure you Cover in SLA Local outages - component failures addressed within the service providers local environment. Return to service should be fast with minimal outage Planned maintenance that will include all hardware, operating system and software patching and upgrades Data protection – data loss due to failure of storage Corruption protection –physical and logical corruptions Disaster Recovery - handles failures which cannot be addressed at the local/primary site or local/primary site is unavailable Human errors - are often limited and can at times be quickly reparable, but at times errors with very large impact may take a significant effort and time to correct

14. Service Level Offerings from Oracle as Example

15. What is Database as a Service (DBaaS) A Database centric and specific Platform as a Service implementation. A managed service, offered on a pay-per-usage basis, that provides on- demand access to a database for the storage of application data. Sometimes called Cloud database Cloud based approach to the storage and management of structured data Concepts can be applied to PUBLIC and Private database as a service Fewer then 1% of Business do it today, but that number is growing Combines Software As a Service, Hardware/Infrastructure As a Service as database software and hardware are involved to provide the database service and the service typically involves the database software and infrastructure as part of the service.

16. What DBaaS is not DBA’s can not wash their hands off. Your neck is still on the line.  Application and Database Design is still end user responsibility  Application and Database Tuning is still end user responsibility  Application availability is still the client responsibility. Service Provider Responsibility  Database is open and available for usage  SLA’s are generic DBaaS is not a licensing alternative  Shifts licensing from a Cap Ex to an OpEx Model  Reusing your existing licenses – that is a part of the negotiation This is not the same as Database Consolidation  Though database consolidation is often a derived effect and impact

17. Database As a Service Model Running Database in the Cloud is not the same as Database as a Service running a database in the cloud is different.  Operating System  Database Software is installed and managed by you the user.  Pay by virtual machine resources including storage  Usually more isolated by the virtualization  This is Really Infrastructure as a Service as environment is provisioned to user not database. True Database as a Service (Provider Managed)  Service Provider Installs database  Service Provider Maintains OS  Pay by Database Usage  Service Provided provides backup  Typically not as isolated as much as when running database in the cloud.  Service Provider does not include tuning, etc.

18. Components of Database As a Service Infrastructure / Hardware  Hosted Infrastructure/Hardware and corresponding operating system  Management of Hardware/Infrastructure Database Software  Can be Managed by the provider or by the user of the service  Many Database Types available most commonly recognized are  MySQL  Oracle  MS SQL Server  PostgreSQL  SAP HANA Database  Creation, migration, management can be on user of the service or can be contracted to service provider providing the Database as a service or contracted to a 3 rd party Managed Service provider.

19. Advantages Elasticity:Provide flexible, scalable on demand Agility:Goal to provide easy management Self Service:Self Service provisioning Charge Back:Monitoring for tracking performance, usage and issue alerting Re-Use:Gone when no longer needed, do not have to have or maintain long term.

20. Drawbacks Lack of control over infrastructure components such as storage and server  With lack of control you lose some control over database, network, server and disk resources which can affect performance, security and ultimate overall experience and ability to utilize Database as a Service. Network performance can pose challenges  Most Database as a Service does not offer different levels of network bandwidth which may be required by certain applications.  May need to move to Infrastructure as a Service and lose some benefits of Database as a service in this case. Some features may not be available such as partitioning and data compression  Some database features may not be part of the service therefore limiting what databases can actually be place in Database as a Service. Data ownership  You retain the ownership of your data within the database  Just Because you own the data does not mean you have full control

21. Drawbacks Security  This is the primary concern and reason why cloud adoption can be a challenge for organizations esp. organization with strict compliance requirements.  Security in Database as a service can be more limited then when running a database in the cloud using infrastructure as a service, be aware of this so you know what data you want to consider putting in the DBaaS and make sure your requirements are covered.

22. Common Drivers/Usage of Database As a Service Specialized Database/Single Purpose Database Small Business with lower IT Support Resources Proof of Concept Environments  NoSQL  Big Data Address Provisioning and database sprawl No long term commitments to utilization so used for short term projects No Need to manage the environment which will free Internal IT resources for critical environments. Good for development environments and fits well into Scrum Teams were scrums teams can have their own development environments and can come and go with the development lifecycles.

23. Understand How Database as a Service use will impact Your Business Deployment lifecycle  Understand how cloud will be used in the development lifecycle  Understand how development lifecycle changes when cloud is used  Control mechanisms for Cloud environments (do not want to expand without checks and balances) IT Support Structure  Who supports what? IT Standards  How Cloud/DBaaS fits into your existing IT standards. Governance  Who is in control of the cloud resources, manages expansion, new environments, etc. Operationalization within the organization  Supporting as part of normal operations is key to success Impact to People and Processes

24. Technologies Enabling DBaaS Generic  Virtualization (Oracle VM, VM Ware, etc.)  Clustering  Converged Infrastructure  Appliance Architecture  Oracle Enterprise Linux Oracle Database Specific  RAC  Pluggable Databases (Multi-Tenant)  Exadata Database Machine  Inter & Intra DB resource Management  Oracle Enterprise Manager 12c  Oracle VM  Oracle Enterprise Linux

25. Technologies Enabling DBaaS MySQL - Trove to deliver MySQL Database as a Service  Tesora is the commercial version  Open Stack DBaaS framework, Open Stack means more then Just MySQL  Web Based API  Build your own DBaaS  Components  trove-api  trove-taskmanager  trove-guestagent  Faster Provisioning  Backups for Databases  Launch a new database based on a backup  Run Public Clouds  HP  Rackspace  Run Private Clouds  eBay

26. Technologies Enabling DBaaS MySQL Enterprise Features (** MySQL Enterprise Edition)  MySQL Enterprise Monitor **  MySQL Enterprise Encryption **  MySQL Enterprise Firewall **  MySQL Enterprise Authentication **  MySQL Enterprise Backup **  MySQL Replication  Oracle Clusterware Agent for MySQL  XAG Agent for MySQL provides an HA Service for MySQL  MySQL Cluster  Synchronous Replication  Automatic Failover  Self Healing

27. Oracle Specific technologies – A further look RAC  Large Cluster environments that can support many databases across many servers  Control what databases run on what servers in the cluster  Can spawn new databases and new database servers quickly.  Remove older unused databases quickly. Pluggable database  Deploy new databases quickly  Remove old unused databases quickly  Resource management  DB Upgrades can easily un-plug and plug in for upgrade  DB Administration  can do a lot of administration isolated within the Container  Backup / Recovery at the pluggable database level.

28. Oracle Specific technologies – A further look Exadata Database Machine  IORM  Ability to control I/O resources so that a shared environment can not consume all available I/O Resources  High Speed / High Performance  Exadata is a High Performance Platform  Exadata is a Highly Available Platform  RAC / Database 12c with pluggable databases  Able to run Oracle VM to virtualize Oracle Enterprise Manager 12c  Manage the Cloud  Servers  Databases  Application Servers  Storage  Exadata

29. Oracle Specific technologies – A further look Oracle VM  Oracle virtualization works on Exadata, RAC and single instance databases  Fast provisioning of new environments  Provisioning of standard database environments (enforce and build to standard automatically)  Can be used free to support non-production clouds Oracle Enterprise Linux  Enterprise Linux that can be used in development free of charge  Be the same Linux as used in production  Only pay when support is needed.  Controls license costs when cloud expands and new environments provisioned

30. 30 Any Further Questions?