Downloaded 41 times
![IVS CTO Night And Day 2018 Winter - [re:Cap] AWS Managed Blockchain & Amazon ...](https://cdn.slidesharecdn.com/ss_thumbnails/ctonight2018blockchain-190115184259-thumbnail.jpg?width=640&height=640&fit=bounds)
Amazon Managed Blockchain and Quantum Ledger Database QLDB
- 1. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. John Yeung, Solutions Architect 26 April 2019. DTL101 Taipei Tech Summit Blockchain related services on AWS Amazon Managed Blockchain & Ledger Database
- 2. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Our Portfolio Broad and deep portfolio, purpose-built for builders Redshift Data warehousing EMR Hadoop + Spark Athena Interactive analytics Kinesis Data Analytics Real time Elasticsearch Service Operational Analytics RDS MySQL, PostgreSQL, MariaDB, Oracle, SQL Server Aurora MySQL, PostgreSQL QuickSight SageMaker DynamoDB Key value, Document ElastiCache Redis, Memcached Neptune Graph Timestream Time Series QLDB Ledger Database S3/Glacier Glue ETL & Data Catalog Lake Formation Data Lakes Database Migration Service | Snowball | Snowmobile | Kinesis Data Firehose | Kinesis Data Streams Data Movement Analytics Databases Business Intelligence & Machine Learning Data Lake Managed Blockchain Blockchain Templates Blockchain RDS on VMware
- 3. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Quantum Ledger Database QLDB Managed Blockchain Two new products: QLDB and Managed Blockchain Our Focus
- 4. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Two Key Questions: Why need Blockchain? Why use Amazon Managed Blockchain and Ledger Database? Let’s see how customers say.
- 5. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. “ConsenSys and AWS coming together to deliver a next generation Enterprise Ethereum service is a complete game changer.” —Ron Resnick EEA Executive Director a ConsenSys company
- 6. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. “Given our vast partner ecosystem, we are exploring the decentralization and immutable tracking benefits of blockchain for potential applications in our insurance business. We believe blockchain can improve the transparency and efficiency for stakeholders in these networks to transact, while still maintaining an independently verifiable lineage of activities. However, blockchain frameworks are complex and difficult to operate. With Amazon Managed Blockchain, we can now easily create Hyperledger Fabric blockchain networks to test and learn without worrying about managing the underlying infrastructure, networking, and software configuration.” —Daniel Johnson CTO and Head of Innovation, Guardian Life Insurance Company The Guardian Life Insurance Company of America is one of the largest mutual life insurance companies in the United States.
- 7. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. “As critical financial market infrastructure, the industry relies on us to provide innovative solutions that reduce risk, increase transparency and evolve with market and regulatory needs. We believe that blockchain technology represents a generational opportunity to re–imagine post–trade infrastructure. We are pleased to be using Amazon Managed Blockchain to explore possibilities with Hyperledger Fabric, where we can continue to lead industry initiatives around the exploration and adoption of blockchain. Amazon Managed blockchain automates the deployment of blockchain infrastructure, bringing high availability and durability in a fully managed package, accelerating the adoption of distributed ledger technology.” —Rob Palatnick Managing Director, Chief Technology Architect, DTCC The Depository Trust & Clearing Corporation DTCC is an American post-trade financial services company providing clearing and settlement services to the financial markets.
- 8. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. “Healthdirect Australia operates in a heavily regulated industry, and it is critical that our compliance data is correct and auditable. With Amazon QLDB we look forward to having a complete and verifiable history of every change in our system, making it simple to audit when and how we arrived at our current state. Regulatory compliance is fact of life for healthcare companies, and Amazon QLDB enables us to easily track the controls we have in place and understand how they have changed over time.” —Bruce Haefele General Manager, Technology, Healthdirect Australia Healthdirect Australia is a national public health information service in Australia, offering access to free health helplines as well as online health information and advice.
- 9. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Why we can’t handle these needs with our relational database technologies?
- 10. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Challenges Customers Face Difficult to manage & scale (e.g. audit tables, stored procedures, storage, etc.) Impossible to verify (e.g. can permanently modify or delete data) Traditional Database Approaches Error prone and incomplete (i.e. trade-off between completeness and scale/performance) Resource intensive (i.e. hard to scale and handling big tables)
- 11. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Why need Blockchain? It enables us to build applications where multiple parties can record transactions without the need for a trusted, central authority to ensure these records are verified and secure, i.e. De-centralized, Immutable, Verifiable and Transparent Capabilities.
- 12. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Challenges Customers Face Hard to scale (i.e. Scalability and performance) Difficult to maintain (e.g. Co-ordinating upgrades) Designed for a different purpose (i.e. Decentralization) Adds unnecessary complexity (e.g. Managing the network and run nodes) Blockchain & Distributed Ledgers
- 13. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Why use Amazon Managed Blockchain and Ledger Database? These are fully managed services, removing the complexity but having the scalability of managing blockchain networks and ledger databases.
- 14. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Key steps of the managed blockchain Amazon Managed Blockchain (Preview)
- 15. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Amazon Quantum Ledger Database (QLDB) (Preview) Fully managed ledger database Track and verify history of all changes made to your application’s data Immutable Maintains a sequenced record of all changes to your data, which cannot be deleted or modified; you have the ability to query and analyze the full history Cryptographically verifiable Uses cryptography to generate a secure output file of your data’s history Easy to use Easy to use, letting you use familiar database capabilities like SQL APIs for querying the data Highly scalable Delivers greater performance and transactions per second as ledgers in common blockchain frameworks
- 16. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Amazon QLBD vs. Amazon Managed Blockchain Amazon QLDB Amazon Managed Blockchain Central trusted authority Track and verify transactions with centralized ownership Ledger is immutable and cryptographically verifiable Ledger is owned by a trusted and centralized authority No central trusted authority Execute transactions and contracts with decentralized ownership Ledger is immutable and cryptographically verifiable Each party maintains their own copy of the ledger Use Ethereum or Hyperledger Fabric to build blockchain networks
- 17. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. For customers that need to maintain a centralized ledger that records all changes, with immutable and verifiable capabilities, they go for QLDB. Amazon QLBD vs. Amazon Managed Blockchain For customers that want to have the immutable and verifiable capabilities by a ledger, and allow multiple parties to transact and share data without a trusted central authority, they go for Managed Blockchain.
- 18. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Can we leverage both of them? We can replicate blockchain network activity data from Managed Blockchain to QLDB for secure storage and off-chain analytics.
- 19. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Ledger Database Concepts C | H J Journal C | H Current | History Current | History Journal Ledger comprises J L Ledger databaseL Journal determines Current | History
- 20. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration
- 21. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration ID Manufacturer Model Year VIN Owner ID Version Start Manufacturer Model Year VIN Owner J history.cars H current.cars C
- 22. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration ID Manufacturer Model Year VIN Owner ID Version Start Manufacturer Model Year VIN Owner J history.cars H INSERT INTO cars << { 'Manufacturer':'Tesla', 'Model':'Model S', 'Year':'2012', 'VIN':'123456789', 'Owner':'Traci Russell' } >>current.cars C
- 23. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration ID Manufacturer Model Year VIN Owner ID Version Start Manufacturer Model Year VIN Owner J history.cars H INSERT INTO cars << { 'Manufacturer':'Tesla', 'Model':'Model S', 'Year':'2012', 'VIN':'123456789', 'Owner':'Traci Russell' } >> INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1)
- 24. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration ID Version Start Manufacturer Model Year VIN Owner J history.cars H INSERT INTO cars << { 'Manufacturer':'Tesla', 'Model':'Model S', 'Year':'2012', 'VIN':'123456789', 'Owner':'Traci Russell' } >> INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) ID Manufacturer Model Year VIN Owner 1 Tesla Model S 2012 123456789 Traci Russell
- 25. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT INTO cars << { 'Manufacturer':'Tesla', 'Model':'Model S', 'Year':'2012', 'VIN':'123456789', 'Owner':'Traci Russell' } >> INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) ID Manufacturer Model Year VIN Owner 1 Tesla Model S 2012 123456789 Traci Russell ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell
- 26. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) ID Manufacturer Model Year VIN Owner 1 Tesla Model S 2012 123456789 Traci Russell ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell
- 27. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) ID Manufacturer Model Year VIN Owner 1 Tesla Model S 2012 123456789 Traci Russell ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell UPDATE cars SET owner = 'Ronnie Nash' WHERE VIN = '123456789'
- 28. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) ID Manufacturer Model Year VIN Owner 1 Tesla Model S 2012 123456789 Traci Russell ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell UPDATE cars ID:1 Owner: Ronnie Nash Metadata: { Date:08/03/2013 } H (T2) UPDATE cars SET owner = 'Ronnie Nash' WHERE VIN = '123456789'
- 29. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) ID Manufacturer Model Year VIN Owner 1 Tesla Model S 2012 123456789 Traci Russell ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell UPDATE cars ID:1 Owner: Ronnie Nash Metadata: { Date:08/03/2013 } H (T2) UPDATE cars SET owner = 'Ronnie Nash' WHERE VIN = '123456789'
- 30. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) UPDATE cars ID:1 Owner: Ronnie Nash Metadata: { Date:08/03/2013 } H (T2) ID Manufacturer Model Year VIN Owner 1 Tesla Model S 2012 123456789 Traci Russell ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell 1 2 08/03/2013 Tesla Model S 2012 123456789 Ronnie Nash UPDATE cars SET owner = 'Ronnie Nash' WHERE VIN = '123456789'
- 31. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) UPDATE cars ID:1 Owner: Ronnie Nash Metadata: { Date:08/03/2013 } H (T2) ID Manufacturer Model Year VIN Owner 1 Tesla Model S 2012 123456789 Ronnie Nash ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell 1 2 08/03/2013 Tesla Model S 2012 123456789 Ronnie Nash UPDATE cars SET owner = 'Ronnie Nash' WHERE VIN = '123456789'
- 32. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) UPDATE cars ID:1 Owner: Ronnie Nash Metadata: { Date:08/03/2013 } H (T2) ID Manufacturer Model Year VIN Owner 1 Tesla Model S 2012 123456789 Ronnie Nash ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell 1 2 08/03/2013 Tesla Model S 2012 123456789 Ronnie Nash
- 33. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) UPDATE cars ID:1 Owner: Ronnie Nash Metadata: { Date:08/03/2013 } H (T2) ID Manufacturer Model Year VIN Owner 1 Tesla Model S 2012 123456789 Ronnie Nash ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell 1 2 08/03/2013 Tesla Model S 2012 123456789 Ronnie Nash DELETE FROM cars WHERE VIN = '123456789'
- 34. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) UPDATE cars ID:1 Owner: Ronnie Nash Metadata: { Date:08/03/2013 } H (T2) ID Manufacturer Model Year VIN Owner 1 Tesla Model S 2012 123456789 Ronnie Nash ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell 1 2 08/03/2013 Tesla Model S 2012 123456789 Ronnie Nash DELETE cars ID:1 Metadata: { Date: 09/02/2016 } H (T3) DELETE FROM cars WHERE VIN = '123456789'
- 35. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) UPDATE cars ID:1 Owner: Ronnie Nash Metadata: { Date:08/03/2013 } H (T2) ID Manufacturer Model Year VIN Owner ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell 1 2 08/03/2013 Tesla Model S 2012 123456789 Ronnie Nash DELETE cars ID:1 Metadata: { Date: 09/02/2016 } H (T3) DELETE FROM cars WHERE VIN = '123456789'
- 36. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Step-by-Step Illustration J history.cars H INSERT cars ID:1 Manufacturer: Tesla Model: Model S Year: 2012 VIN: 123456789 Owner: Traci Russell Metadata: { Date:07/16/2012 } current.cars C H (T1) UPDATE cars ID:1 Owner: Ronnie Nash Metadata: { Date:08/03/2013 } H (T2) ID Manufacturer Model Year VIN Owner DELETE cars ID:1 Metadata: { Date: 09/02/2016 } H (T3) ID Version Start Manufacturer Model Year VIN Owner 1 1 07/16/2012 Tesla Model S 2012 123456789 Traci Russell 1 2 08/03/2013 Tesla Model S 2012 123456789 Ronnie Nash 1 3 09/02/2016 Deleted DELETE FROM cars WHERE VIN = '123456789'
- 37. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Summary Why need Blockchain Why use Amazon Managed Blockchain & Ledger Database Differences between these two products Call-for-actions: Sign-up the Previews
- 38. © 2019, AmazonWeb Services, Inc. or its Affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Thank You! Contact: jyeung@amazon.com