DOCSLIB.ORG

Amazon Aurora: Amazon’S New Relational Database Engine

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Amazon Aurora: Amazon’S New Relational Database Engine BERLIN ©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved Amazon Aurora: Amazon’s New Relational Database Engine Carlos Conde – Technology Evangelist @caarlco ©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved Current DB architectures are monolithic SQL Multiple layers of Transactions functionality all on a Caching single box Logging Current DB architectures are monolithic Application Even when you scale it out, you’re still SQL SQL replicating the same Transactions Transactions Caching Caching stack Logging Logging Current DB architectures are monolithic Application Even when you scale it out, you’re still SQL SQL replicating the same Transactions Transactions Caching Caching stack Logging Logging Current DB architectures are monolithic Application Even when you scale it out, you’re still SQL SQL replicating the same Transactions Transactions Caching Caching stack Logging Logging Storage This is a problem. For cost. For flexibility. And for availability. Reimagining the relational database What if you were inventing the database today? You wouldn’t design it the way we did in 1970. At least not entirely. You’d build something that can scale out, that is self-healing, and that leverages existing AWS services. Relational databases reimagined for the cloud Speed and availability of high-end commercial databases Simplicity and cost-effectiveness of open source databases Drop-in compatibility with MySQL Simple pay as you go pricing Delivered as a managed service A service-oriented architecture applied to the database Data Plane Control Plane • Moved the logging and storage layer into a multi-tenant, scale-out SQL database-optimized storage service Transactions Caching Amazon • Integrated with other AWS services DynamoDB like Amazon EC2, Amazon VPC, Amazon DynamoDB, Amazon SWF, and Amazon Route 53 for control Logging + Storage plane operations Amazon SWF • Integrated with Amazon S3 for continuous backup with 99.999999999% durability Amazon S3 Amazon Route 53 Aurora preview • Sign up for preview access at: https://aws.amazon.com/rds/aurora/preview • Now available in US West (Oregon) and EU (Ireland), in addition to US East (N. Virginia) • Thousands of customers already invited to the limited preview • Now moving to unlimited preview; accepting all requests in 2–3 weeks • Full service launch in the coming months Enterprise grade, open source pricing vCPU Mem Hourly Price Simple pricing db.r3.large 2 15.25 $0.29 • No licenses db.r3.xlarge 4 30.5 $0.58 • No lock-in db.r3.2xlarge 8 61 $1.16 • Pay only for what you use db.r3.4xlarge 16 122 $2.32 db.r3.8xlarge 32 244 $4.64 Discounts • 44% with a 1-year RI • 63% with a 3-year RI • Storage consumed, up to 64 TB, is $0.10/GB-month • IOs consumed are billed at $0.20 per million I/O • Prices are for Virginia Aurora Works with Your Existing Apps Establishing our ecosystem “It is great to see Amazon Aurora remains MySQL compatible; MariaDB connectors work with Aurora seamlessly. Today, customers can take MariaDB Enterprise with MariaDB MaxScale drivers and connect to Aurora, MariaDB, or MySQL without worrying about compatibility. We look forward to working with the Aurora team in the future to further accelerate innovation within the MySQL ecosystem.”— Roger Levy, VP Products, MariaDB Business Intelligence Data Integration Query and Monitoring SI and Consulting Amazon Aurora Is Easy to Use Simplify database management • Create a database in minutes • Automated patching • Push-button scale compute • Continuous backups to S3 Amazon RDS • Automatic failure detection and failover Simplify storage management • Read replicas are available as failover targets—no data loss • Instantly create user snapshots—no performance impact • Continuous, incremental backups to S3 • Automatic storage scaling up to 64 TB—no performance or availability impact • Automatic restriping, mirror repair, hot spot management, encryption Simplify data security • Encryption to secure data at rest Application – AES-256; hardware accelerated – All blocks on disk and in Amazon S3 are encrypted – Key management via AWS KMS SQL Transactions • SSL to secure data in transit Caching • Network isolation via Amazon VPC by default • No direct access to nodes Storage • Supports industry standard security and data protection certifications Amazon S3 Amazon Aurora Is Highly Available Aurora storage • Highly available by default – 6-way replication across 3 AZs AZ 1 AZ 2 AZ 3 – 4 of 6 write quorum • Automatic fallback to 3 of 4 if an AZ is unavailable – 3 of 6 read quorum SQL Transactions • SSD, scale-out, multi-tenant storage – Seamless storage scalability Caching – Up to 64 TB database size – Only pay for what you use • Log-structured storage – Many small segments, each with their own redo logs – Log pages used to generate data pages – Eliminates chatter between database and storage Amazon S3 Consistent, low-latency writes MySQL with standby Amazon Aurora AZ 1 AZ 2 AZ 1 AZ 2 AZ 3 Primary Standby Primary Replica Instance Instance Instance Instance async 4/6 quorum Amazon Elastic EBS PiTR Block Store (EBS) Sequential Sequential write write Distributed writes EBS EBS mirror mirror Amazon S3 Amazon S3 Improvements Type of writes • Consistency—tolerance to outliers Log records • Latency— synchronous vs. asynchronous replication Binlog Data • Significantly more efficient use of network I/O Double-write buffer FRM files, metadata Self-healing, fault-tolerant • Lose two copies or an AZ failure without read or write availability impact • Lose three copies without read availability impact • Automatic detection, replication, and repair AZ 1 AZ 2 AZ 3 AZ 1 AZ 2 AZ 3 SQL SQL Transaction Transaction Caching Caching Read availability Read and write availability Instant crash recovery Traditional databases Amazon Aurora • Have to replay logs since the last • Underlying storage replays redo checkpoint records on demand as part of a disk read • Single-threaded in MySQL; requires a large number of disk • Parallel, distributed, asynchronous accesses Crash at T0 requires Crash at T0 will result in redo a re-application of the logs being applied to each segment SQL in the redo log since on demand, in parallel, asynchronously last checkpoint Checkpointed Data Redo Log T0 T0 Survivable caches • We moved the cache out of Caching process is outside the DB process the database process and remains warm across a database restart SQL SQL SQL • Cache remains warm in the Transactions Transactions Transactions event of a database restart Caching Caching Caching • Lets you resume fully loaded operations much faster • Instant crash recovery + survivable cache = quick and easy recovery from DB failures Multiple failover targets—no data loss MySQL Master MySQL Replica Aurora Master Aurora Replica Single-threaded Page cache binlog apply invalidation 70% Write 70% Write 70% Write 100% New Reads 30% Read 30% New Reads 30% Read Data Volume Data Volume Shared Multi-AZ Storage MySQL read scaling • Replicas must replay logs • Replicas place additional load on master • Replica lag can grow indefinitely • Failover results in data loss Simulate failures using SQL • To cause the failure of a component at the database node: ALTER SYSTEM CRASH [{INSTANCE | DISPATCHER | NODE}] • To simulate the failure of disks: ALTER SYSTEM SIMULATE percent_failure DISK failure_type IN [DISK index | NODE index] FOR INTERVAL interval • To simulate the failure of networking: ALTER SYSTEM SIMULATE percent_failure NETWORK failure_type [TO {ALL | read_replica | availability_zone}] FOR INTERVAL interval Amazon Aurora Is Fast Write performance (console screenshot) • MySQL Sysbench • R3.8XL with 32 cores and 244 GB RAM • 4 client machines with 1,000 threads each Read performance (console screenshot) • MySQL Sysbench • R3.8XL with 32 cores and 244 GB RAM • Single client with 1,000 threads Read replica lag (console screenshot) • Aurora Replica with 7.27 ms replica lag at 13.8 K updates/second • MySQL 5.6 on the same hardware has ~2 s lag at 2 K updates/second Writes scale with table count Write Performance and Table Count 70 MySQL MySQL RDS MySQL Amazon Tables I2.8XL I2.8XL 30K IOPS 60 Aurora Local SSD RAM Disk (Single AZ) 50 10 60,000 18,000 22,000 25,000 40 100 66,000 19,000 24,000 23,000 30 ThousandsWrites of per Second 1,000 64,000 7,000 18,000 8,000 20 10 10,000 54,000 4,000 8,000 5,000 - 10 100 1.000 10.000 Number of Tables Write-only workload 1,000 connections Aurora Query cache (default on for Amazon Aurora, off for MySQL) MySQL on I2.8XL MySQL on I2.8XL with RAM Disk RDS MySQL with 30,000 IOPS (Single AZ) Better concurrency Write Performance and Concurrency 120 RDS MySQL Amazon 100 Connections 30K IOPS Aurora (Single AZ) 80 50 40,000 10,000 60 500 71,000 21,000 40 5,000 110,000 13,000 ThousandsWrites of per Second 20 - 50 500 5.000 OLTP Workload Concurrent Connections Variable connection count 250 tables Query cache (default on for Amazon Aurora, off for MySQL) Aurora RDS MySQL with 30,000 IOPS (Single AZ) Caching improves performance Performance with query cache on and off Amazon Amazon RDS MySQL RDS MySQL 400 Aurora Aurora 30K IOPS 30K IOPS R/W Ratio Without With Without With 350 Caching Caching Caching Caching 300 100/0 160,000 375,000 35,000 19,000 250 50/50 130,000 93,000 24,000 20,000 200 150 0/100 64,000 64,000 16,000 16,000 100 ThousandsOperations/Second of 50 - 100/0 50/50 0/100 OLTP workload Read/Write Ratio 1,000 connections Aurora without Caching 250 tables Aurora with Caching Query cache on/off tested RDS MySQL;30,000 IOPS (Single AZ) - without caching RDS MySQL;30,000 IOPS (Single AZ) - with caching Replicas have up to 400 times less lag Read Replica Lag RDS MySQL Updates/ Amazon 350.000 30K IOPS Second Aurora (Single AZ) 300.000 1,000 2.62 ms 0 s 250.000 2,000 3.42 ms 1 s 200.000 5,000 3.94 ms 60 s 150.000 Read Replica Lag in Milliseconds 100.000 10,000 5.38 ms 300 s 50.000 2,6 3,4 3,9 5,4 Write workload 0 1.000 2.000 5.000 10.000 250 tables Updates per Second Query cache on for Amazon Aurora, off for MySQL (best settings) Aurora RDS MySQL;30,000 IOPS (Single AZ) BERLIN.
Load more

Recommended publications
  • Introducing Amazon RDS for Aurora Chris Littlefield, AWS Certified Solutions Architect – Associate Level, AWS Certified Sysops Administrator – Associate Level
    Expert Reference Series of White Papers Introducing Amazon RDS for Aurora 1-800-COURSES www.globalknowledge.com Introducing Amazon RDS for Aurora Chris Littlefield, AWS Certified Solutions Architect – Associate Level, AWS Certified SysOps Administrator – Associate Level Introduction The following document provides an overview of one of the latest offerings from cloud leader Amazon Web Services (AWS). It’s a product that will enable powerful, massively scalable relational databases in Amazon’s cloud environment. The product was designed, built, and tested in secret over the past three years, and now it is nearly ready for production workloads. Some of its detailed design remains confidential, so we’ll present the released features and functionality, as well as pricing for this exciting new product. Background In November 2014, at Amazon Web Services’ annual conference re:Invent, Andy Jassy introduced a series of revolutionary new products. Among those new products is the product described in this paper, which is based on AWS’s hugely successful Relational Database Service (RDS). So what’s this new product, you ask? It’s Amazon Aurora for RDS. Aurora is MySQL compatible database solution that will enable highly scalable databases running across multiple AWS availability zones, at a very low price point. It’s designed to deliver the performance and availability of commercial grade databases at the simplicity and price point of open source databases. What is Amazon Aurora? Aurora is a MySQL compatible database engine that far exceeds the current size limitations of relational databases running on RDS. It spans three AWS availability zones within a region. The great news is that if you already use or are familiar with RDS, you’re already going to be comfortable configuring Aurora.
    [Show full text]
  • Rose Gardner Mysteries
    JABberwocky Literary Agency, Inc. Est. 1994 RIGHTS CATALOG 2019 JABberwocky Literary Agency, Inc. 49 W. 45th St., 12th Floor, New York, NY 10036-4603 Phone: +1-917-388-3010 Fax: +1-917-388-2998 Joshua Bilmes, President [email protected] Adriana Funke Karen Bourne International Rights Director Foreign Rights Assistant [email protected] [email protected] Follow us on Twitter: @awfulagent @jabberworld For the latest news, reviews, and updated rights information, visit us at: www.awfulagent.com The information in this catalog is accurate as of [DATE]. Clients, titles, and availability should be confirmed. Table of Contents Table of Contents Author/Section Genre Page # Author/Section Genre Page # Tim Akers ....................... Fantasy..........................................................................22 Ellery Queen ................... Mystery.........................................................................64 Robert Asprin ................. Fantasy..........................................................................68 Brandon Sanderson ........ New York Times Bestseller.......................................51-60 Marie Brennan ............... Fantasy..........................................................................8-9 Jon Sprunk ..................... Fantasy..........................................................................36 Peter V. Brett .................. Fantasy.....................................................................16-17 Michael J. Sullivan ......... Fantasy.....................................................................26-27
    [Show full text]
  • Amazon Documentdb Deep Dive
    DAT326 Amazon DocumentDB deep dive Joseph Idziorek Antra Grover Principal Product Manager Software Development Engineer Amazon Web Services Fulfillment By Amazon © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Agenda What is the purpose of a document database? What customer problems does Amazon DocumentDB (with MongoDB compatibility) solve and how? Customer use case and learnings: Fulfillment by Amazon What did we deliver for customers this year? What’s next? © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Purpose-built databases Relational Key value Document In-memory Graph Search Time series Ledger Why document databases? Denormalized data Normalized data model model { 'name': 'Bat City Gelato', 'price': '$', 'rating': 5.0, 'review_count': 46, 'categories': ['gelato', 'ice cream'], 'location': { 'address': '6301 W Parmer Ln', 'city': 'Austin', 'country': 'US', 'state': 'TX', 'zip_code': '78729'} } Why document databases? GET https://api.yelp.com/v3/businesses/{id} { 'name': 'Bat City Gelato', 'price': '$', 'rating': 5.0, 'review_count': 46, 'categories': ['gelato', 'ice cream'], 'location': { 'address': '6301 W Parmer Ln', 'city': 'Austin', 'country': 'US', 'state': 'TX', 'zip_code': '78729'} } Why document databases? response = yelp_api.search_query(term='ice cream', location='austin, tx', sort_by='rating', limit=5) Why document databases? for i in response['businesses']: col.insert_one(i) db.businesses.aggregate([ { $group: { _id: "$price", ratingAvg: { $avg: "$rating"}} } ]) db.businesses.find({
    [Show full text]
  • Web Application Hosting in the AWS Cloud AWS Whitepaper Web Application Hosting in the AWS Cloud AWS Whitepaper
    Web Application Hosting in the AWS Cloud AWS Whitepaper Web Application Hosting in the AWS Cloud AWS Whitepaper Web Application Hosting in the AWS Cloud: AWS Whitepaper Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Web Application Hosting in the AWS Cloud AWS Whitepaper Table of Contents Abstract ............................................................................................................................................ 1 Abstract .................................................................................................................................... 1 An overview of traditional web hosting ................................................................................................ 2 Web application hosting in the cloud using AWS .................................................................................... 3 How AWS can solve common web application hosting issues ........................................................... 3 A cost-effective alternative to oversized fleets needed to handle peaks ..................................... 3 A scalable solution to handling unexpected traffic
    [Show full text]
  • Planning and Designing Databases on AWS (AWS-PD-DB)
    Planning and Designing Databases on AWS (AWS-PD-DB) COURSE OVERVIEW: In this course, you will learn about the process of planning and designing both relational and nonrelational databases. You will learn the design considerations for hosting databases on Amazon Elastic Compute Cloud (Amazon EC2). You will learn about our relational database services including Amazon Relational Database Service (Amazon RDS), Amazon Aurora, and Amazon Redshift. You will also learn about our nonrelational database services including Amazon DocumentDB, Amazon DynamoDB, Amazon ElastiCache, Amazon Neptune, and Amazon QLDB. By the end of this course, you will be familiar with the planning and design requirements of all 8 of these AWS databases services, their pros and cons, and how to know which AWS databases service is right for your workloads. WHO WILL BENEFIT FROM THIS COURSE? • Data platform engineers • Database administrators • Solutions architects • IT professionals PREREQUISITES: We recommend that attendees of this course have previously completed the following AWS courses: • AWS Database Offerings digital training • Data Analytics Fundamentals digital training • Architecting on AWS classroom training COURSE OBJECTIVES: After completion of this course, students will be able to... • Apply database concepts, database management, and data modeling techniques • Evaluate hosting databases on Amazon EC2 instances • Evaluate relational database services (Amazon RDS, Amazon Aurora, and Amazon Redshift) and their features • Evaluate nonrelational database services
    [Show full text]
  • Amazon Aurora
    D A T 2 0 2 - R What's new in Amazon Aurora Tony Petrossian GM Amazon Aurora Amazon Web Services © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Amazon Aurora Enterprise database at open source price Delivered as a managed service Drop-in compatibility with MySQL and PostgreSQL Simplicity and cost-effectiveness of open-source databases Throughput and availability of commercial databases Amazon Aurora Simple pay-as-you-go pricing 4 © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Database layers SQL Transactions Multiple layers Caching of processing all in a single Logging & Storage engine Aurora decouples storage and query processing SQL Database Transactions node Caching Amazon Aurora Storage Processing Shared storage volume nodes Storage Storage Scale-out, distributed storage processing architecture Purpose-built log-structured distributed Availability Zone 1 Availability Zone 2 Availability Zone 3 storage system designed for databases SQL SQL SQL Storage volume is striped across hundreds Transactions Transactions Transactions of storage nodes distributed over 3 Caching Caching Caching Instancenodes different Availability Zones Six copies of data, two copies in each Availability Zone to protect against AZ+1 Shared storage volume failures Data is written in 10 GB “protection nodes Storage groups”, growing automatically when needed 8 © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Aurora: Why re-imagine the RDBMS Customers Aurora: Why re-imagine the RDBMS Aurora:
    [Show full text]
  • Amazon Aurora Connector
    Informatica® Cloud Data Integration Amazon Aurora Connector Informatica Cloud Data Integration Amazon Aurora Connector August 2021 © Copyright Informatica LLC 2017, 2021 This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC. U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation is subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License. Informatica, the Informatica logo, Informatica Cloud, and PowerCenter are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html. Other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties. Required third party notices are included with the product. See patents at https://www.informatica.com/legal/patents.html. DISCLAIMER: Informatica LLC provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose.
    [Show full text]
  • Overview of Amazon Web Services
    Overview of Amazon Web Services December 2015 Amazon Web Services Overview December 2015 © 2015, Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. Page 2 of 31 Amazon Web Services Overview December 2015 Contents Contents 3 Introduction 4 What Is Cloud Computing? 4 Six Advantages of Cloud Computing 5 Global Infrastructure 5 Security and Compliance 6 Security 6 Compliance 7 Amazon Web Services Cloud Platform 7 Compute 8 Storage and Content Delivery 12 Database 14 Networking 15 Developer Tools 17 Management Tools 17 Security and Identity 19 Analytics 21 Internet of Things 24 Mobile Services 25 Application Services 26 Enterprise Applications 27 Next Steps 28 Conclusion 29 Contributors 29 Document Revisions 29 Notes 29 Page 3 of 31 Amazon Web Services Overview December 2015 Introduction In 2006, Amazon Web Services (AWS) began offering IT infrastructure services to businesses in the form of web services—now commonly known as cloud computing.
    [Show full text]
  • Modernisation Des Infrastructures Microsoft Et Oracle Sur AWS
    Modernisation des infrastructures Microsoft et Oracle sur AWS François Bouteruche – Senior Specialist SA, Builder © 2020, Amazon Web Services, Inc. or its Affiliates. Business goals & challenges © 2020, Amazon Web Services, Inc. or its Affiliates. What are your business goals? Grow new revenue streams © 2020, Amazon Web Services, Inc. or its Affiliates. The True Value of a Digital Enterprise Empowered Intelligent Decision Better Relationship Sales Teams Making with Customers Revenue Growth Cloud Services SQL .Net Windows Compute, Storage & Networking Operational Overhead Increased Products that Get Data Driven Efficiency Better with Time Discipline © 2020, Amazon Web Services, Inc. or its Affiliates. What are your business goals? Improve operational and financial efficiency © 2020, Amazon Web Services, Inc. or its Affiliates. The True Value of a Digital Enterprise Empowered Intelligent Decision Better Relationship Sales Teams Making with Customers Revenue Growth Cloud Services SQL .Net Windows Compute, Storage & Networking Operational Overhead Increased Products that Get Data Driven Efficiency Better with Time Discipline © 2020, Amazon Web Services, Inc. or its Affiliates. What are your business goals? Lower business risk © 2020, Amazon Web Services, Inc. or its Affiliates. Enterprise Business Transformation Challenge 88% 86% enterprises have a infra spend still cloud-first strategy on-premises © 2020, Amazon Web Services, Inc. or its Affiliates. What customers are facing R e t i r e Innova t e t e c h n i c a l f a s t e r d e b t © 2020, Amazon Web Services, Inc. or its Affiliates. Migration Steps © 2020, Amazon Web Services, Inc. or its Affiliates. Determine your migration path © 2020, Amazon Web Services, Inc.
    [Show full text]
  • Databases on AWS the Right Tool for the Right Job
    Databases on AWS The Right Tool for the Right Job David Gendel, Sr. Solutions Architect, AWS Wednesday, February 17, 2021 © 2021, Amazon Web Services, Inc. or its Affiliates. Traditional Database Architecture Client Tier one database App/Web Tier for all workloads RDBMS © 2021, Amazon Web Services, Inc. or its Affiliates. Traditional Database Architecture • Key-value access Client Tier • Complex queries • OLAP transactions App/Web Tier • Analytics RDBMS All forced into the relational database © 2021, Amazon Web Services, Inc. or its Affiliates. AWS Data Tier Architecture Client Tier On AWS choose best database service for each App/Web Tier workload Data Tier Cache Data Warehouse Time Series Blob Store NoSQL RDBMS Quantum Ledger Search © 2021, Amazon Web Services, Inc. or its Affiliates. Workload Driven Data Store Selection hot reads analytics logging NoSQL complex queries Periodic rich search simple query & transactions data Graph / Key Value / Document Untampered data Data Tier Cache Data Warehouse Time Series Blob Store NoSQL RDBMS Quantum Ledger Search © 2021, Amazon Web Services, Inc. or its Affiliates. AWS Database Services hot reads analytics logging NoSQL complex queries Periodic rich search simple query & transactions data Graph / Key Value / Document Untampered data Data Tier Amazon Amazon Amazon Amazon S3 ElastiCache Redshift Timestream Amazon DynamoDB Amazon Amazon Amazon Neptune / DocumentDB RDS QLDB ElasticSearch © 2021, Amazon Web Services, Inc. or its Affiliates. Easy to Administer Highly Scalable Amazon RDS Available and
    [Show full text]
  • AWS Prescriptive Guidance Migrating Oracle Databases to the AWS Cloud AWS Prescriptive Guidance Migrating Oracle Databases to the AWS Cloud
    AWS Prescriptive Guidance Migrating Oracle databases to the AWS Cloud AWS Prescriptive Guidance Migrating Oracle databases to the AWS Cloud AWS Prescriptive Guidance: Migrating Oracle databases to the AWS Cloud Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. AWS Prescriptive Guidance Migrating Oracle databases to the AWS Cloud Table of Contents Introduction ...................................................................................................................................... 1 Overview ................................................................................................................................... 1 Oracle database migration strategies .................................................................................................... 3 Choosing the right migration strategy .......................................................................................... 3 Online and offline migration ....................................................................................................... 4 Homogeneous database migration ......................................................................................................
    [Show full text]
  • Moving to Managed Databases
    Moving to Managed Databases Sohan Maheshwar Developer Advocate, AWS © 2020, Amazon Web Services, Inc. or its Affiliates. Agenda Why move to managed services? Managed database services Flexible ways to move to AWS databases Resources Q&A © 2020, Amazon Web Services, Inc. or its Affiliates. � TRIVIA TIME � © 2020, Amazon Web Services, Inc. or its Affiliates. Why Move to Managed Databases? © 2020, Amazon Web Services, Inc. or its Affiliates. Self-managing databases is time-consuming, complex, and expensive Hardware and software installation, configuration, patching, backups Performance and high availability issues Capacity planning and scaling clusters for compute and storage Security and compliance © 2020, Amazon Web Services, Inc. or its Affiliates. Fully managed services on AWS Spend time innovating and building new applications, not managing infrastructure Self-managed Fully managed Schema design Query construction You Query optimization Automatic failover Backup and recovery Isolation and security You Industry compliance Push-button scaling AWS Automated patching Advanced monitoring Routine maintenance Built-in best practices © 2020, Amazon Web Services, Inc. or its Affiliates. Answer: Airbnb © 2020, Amazon Web Services, Inc. or its Affiliates. Challenge They experienced service admin challenges with their original provider and wanted to scale business to the next level. Solution They moved from self-managed MySQL to Amazon Aurora MySQL. They use Aurora as the primary transactional database, Amazon DynamoDB for personalized search, and Amazon ElastiCache as in- memory store for sub-millisecond site rendering. Result Initially, the appeal of AWS was the ease of managing and “customizing the stack. It was great to be able to ramp up more servers without having to contact anyone and without having minimum usage commitments.
    [Show full text]