1 / 21

Dynamo: Amazon’s Highly Available Key-value Store

Dynamo: Amazon’s Highly Available Key-value Store. DeCandia , Hastorun , Jampani , Kakulapati , Lakshman , Pilchin , Sivasubramanian , Vosshall , Vogels. PRESENTED BY: KIMIISA OSHIKOJI. OUTLINE. Amazon Dynamo Architecture Performance. AMAZON. Huge Infrastructure

glen
Download Presentation

Dynamo: Amazon’s Highly Available Key-value Store

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Dynamo: Amazon’s Highly Available Key-value Store DeCandia, Hastorun, Jampani, Kakulapati, Lakshman, Pilchin, Sivasubramanian, Vosshall, Vogels PRESENTED BY: KIMIISA OSHIKOJI

  2. OUTLINE • Amazon • Dynamo • Architecture • Performance

  3. AMAZON • Huge Infrastructure • Customer oriented business • Reliability is key

  4. DYNAMO • Data storage system • Flexible • Automated addition and removal of storage nodes

  5. DYNAMO-REQUIREMENTS

  6. DYNAMO-QUERY MODEL • Key identifies operations • Operations don’t require multiple data items • Data to be stored is relatively small

  7. DYNAMO-ACID PROPERTIES

  8. DYNAMO-EFFICINCY

  9. DYNAMO-ASSUMPTIONS • Only used by internal Amazon systems • No security considerations • Limited scalability

  10. DYNAMO-SLA • Service Level Agreement: contract between client and service about their relationship • In Amazon a typical client request involves over 100 services who might have dependencies • SLA are governed by 99.9th percentile

  11. DYNAMO-DESIGN • Focus on correctness of an answer rather than how quickly it can be available • Eventually consistent data store • Writes can never be rejected • 99.9th percentile • Zero-hop DHT

  12. DYNAMO-PRINCIPLES

  13. ARCHITECTURE-STORAGE • Objects stored with a key using: • Get(key): locates object with key and returns object or list of objects with a context • Put(key, context): places an object at a replica along with the key and context • Context: metadata about object

  14. ARCHITECTURE-HASHING

  15. ARCHITECTURE-REPLICATION • Data is replicated on N hosts (N is determined by user) • Coordinator nodes replicate the data for nodes they are responsible for coordinating

  16. ARCHITECTURE-VERSIONING • Multiple versions can exist • Vector clock is used for version control • Vector clock size issue

  17. ARCHITECTURE-FAILURE *Failure are not automatically detected by a central node

  18. ARCHITECTURE-ADDING

  19. PERFORMANCE-BUFFER • System can be optimized without sacrificing the 99.9th percentile • Buffer usage can decrease latency by a factor of 5 during peak traffic times

  20. PERFORMANCE-LOAD DISTRIBUTION *Third strategy is the best in terms of balancing

  21. QUESTIONS?

More Related