DOCSLIB.ORG

Introduction to Amazon Dynamodb - and Some Use Case Examples

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Introduction to Amazon DynamoDB - and some use case examples Pete Naylor Sr Database Specialist SA - AWS © 2020, Amazon Web Services, Inc. or its Affiliates. Agenda • DynamoDB’s place in the history of purpose-built databases • Key concepts • How do I use DynamoDB? - Basic data models and controls • Challenges with changing and imbalanced loads - And how DynamoDB deals with them • Integrated DynamoDB architecture and data flows © 2020, Amazon Web Services, Inc. or its Affiliates. Database evolution and DynamoDB © 2020, Amazon Web Services, Inc. or its Affiliates. DynamoDB history How did we get here? 2004 – Amazon.com operational database scaling woes https://www.cnet.com/news/amazon-com-hit-with-outages/ 2007 – Whitepaper describing internal distributed database solution http://www.allthingsdistributed.com/files/amazon-dynamo-sosp2007.pdf 2012 – Reimagined implementation made available via AWS as DynamoDB https://aws.amazon.com/about-aws/whats-new/2012/01/18/aws-announces-dynamodb/ 2018 – Amazon.com almost entirely migrated to Redshift, Aurora, DynamoDB https://twitter.com/ajassy/status/1060979175098437632 2019 – Continuing rapid innovation informed by unmatched experience http://amzn.to/2fAJXH9 © 2020, Amazon Web Services, Inc. or its Affiliates. DynamoDB history Motivations at Amazon (and elsewhere) 1. Reduce dependence on commercially licensed relational database engines 2. Minimize operational complexity and administrative overhead 3. Provide best possible customer experience across all data indexing needs “A one size fits all database doesn't fit anyone” - Werner Vogels © 2020, Amazon Web Services, Inc. or its Affiliates. Internet-scale applications Users 1M+ Data volume TB-PB-EB Locality Global Performance Milliseconds-microseconds Request rate Millions Access Mobile, IoT, devices Scale Incrementally based on traffic Economics Pay as you go Developer access Instant API access © 2020, Amazon Web Services, Inc. or its Affiliates. © 2020, Amazon Web Services, Inc. or its Affiliates. By: Arturo Pardavila III https://www.flickr.com/photos/apardavila/albums/72157674624352641 Snap (Snapchat) Database writes peak seconds after Chicago Cubs win the World Series. © 2020, Amazon Web Services, Inc. or its Affiliates. A migration from mainframe • Retail business ran on mainframe, which became a bottleneck • Migrated financial transaction data to DynamoDB • Unbound scale for customers and app developers “We built a secure and resilient cloud infrastructure that could solve the scalability and reliability problems with a serverless architecture.” Srini Uppalapati Capital One © 2020, Amazon Web Services, Inc. or its Affiliates. SQL and DynamoDB side by side Traditional SQL DynamoDB Optimized for storage Optimized for compute Normalized/relational Denormalized/hierarchical Ad hoc queries Instantiated views for known patterns Scale vertically Scale horizontally Good for OLAP Built for OLTP at scale © 2020, Amazon Web Services, Inc. or its Affiliates. Core Strengths of DynamoDB Sounds cool, but when should I use it? Considerations: Priorities • SQL / NoSQL • Relational / Non-Relational ü Security • Operational / Analytical ü Durability ü Scalability DynamoDB solves for: • Horizontal scaling ü Availability • Decoupled compute/storage ü Low Latency • Asynchronous roll-ups/aggregations ü Easy to Use • Availability/Durability/Latency ü Easy to Manage • Well-known access patterns • Schema flexibility © 2020, Amazon Web Services, Inc. or its Affiliates. Key concepts © 2020, Amazon Web Services, Inc. or its Affiliates. Scaling databases Traditional SQL NoSQL DB DB DB DB DB DB P1 P2 P3 Pn Scale up Scale out to many shards © 2020, Amazon Web Services, Inc. or its Affiliates. Scaling NoSQL databases Most NoSQL databases DynamoDB DB DB DB DB DB DB DB DB DB P1DB P1DB P1DB P1DB P1DB P1 DB DB DB DB P1DB P1DB P1DB P1DB P1 P1 DB DB DB P1DB P1DB P1DB P1DB P1DB P1 DB DB P1DB P1DB P1DB P1DB P1DB P1DB DB DB P25 P26 P27 P28 P29 P30 Servers and clusters DynamoDB: partitions Basic premise: There is a way to shard data that’s horizontally scalable. © 2020, Amazon Web Services, Inc. or its Affiliates. Incremental scaling with DynamoDB Workload: data volume, reads, writes DynamoDB resources: storage, read, and write capacity © 2020, Amazon Web Services, Inc. or its Affiliates. You work with tables… Table 1 Table 2 Table 3 DynamoDB does the rest under the hood… Server 1 Server N 1K WU or 3K RU T1.p1 T1.pn up to 10 GB © 2020, Amazon Web Services, Inc. or its Affiliates. Terminology Primary key – unique item identifier Items DynamoDB table Sort key conditions: all items Partition Sort key ==, <, >, >=, <= Attributes “begins with” key (optional) “between” - 1:1 relationships - 1:many relationships sorted results - distribute traffic - collect related items counts - collection identity - efficient filtering top/bottom N - sorting © 2020, Amazon Web Services, Inc. or its Affiliates. Global secondary index (GSI) Online indexing Alternate partition (+sort) key for alternate materialized view Capacity provisioned separately from table A1 A2 A3 A4 A5 Table (partition) Up to 20 GSIs per table A2 A1 (part.) (table key) KEYS_ONLY A5 A4 A1 A3 INCLUDE A3 GSIs (part.) (sort) (table key) (projected) A4 A5 A1 A2 A3 (part.) (sort) (table key) (projected) (projected) ALL © 2020, Amazon Web Services, Inc. or its Affiliates. Sharding/partitioning Denormalized Record Partition key DynamoDB table Hash.MIN = 0 Orders 00 Partition A OrderId: 1 CountryCode: 1 Hash(1) = 7B ASIN: [B00X4WHP5E] Keyspace 55 Partition B OrderId: 2 CountryCode : 1 Hash(2) = 48 ASIN: [B00OQVZDJM] AA OrderId: 3 Partition C CountryCode : 1 Hash(3) = CD ASIN: [B00U3FPN4U] FF Hash.MAX = FF Related data is stored together for efficient access © 2020, Amazon Web Services, Inc. or its Affiliates. A view “from a different angle” Three Replicas OrderId: 1 CustomerId: 1 Across 3 Availability ASIN: [B00X4WHP5E] Zones in the Region - one replica is elected to serve as “leader”. Hash(1) = 7B Availability Zone A Availability Zone B Availability Zone C Partition A Partition B Partition C Partition A Partition B Partition C PartitionPartition A A Partition B Partition C Host 1 Host 2 Host 3 Host 4 Host 5 Host 6 Host 7 Host 8 Host 9 CustomerOrdersTable © 2020, Amazon Web Services, Inc. or its Affiliates. Modeling data for DynamoDB © 2020, Amazon Web Services, Inc. or its Affiliates. Partition key • A good sharding (partitioning) scheme affords even distribution of both data and workload as they grow • Key concept: partition key as the dimension of scalability • Distribute traffic and data across partitions – horizontal scaling • Ideal scaling conditions: • The partition key is from a high cardinality set (that grows) • Requests are evenly spread over the key space • Requests are evenly spread over time © 2020, Amazon Web Services, Inc. or its Affiliates. Denormalization Traditional database DynamoDB CART CART CART_ITEM CartId: 1, CartId: 1, ItemId: 2, Qty: 1, Version: v3, Version: v3 CartId: 1 Items: [ {ID: 2, Qty: 1}, {ID: 5, Qty: 2}] Normalized schema: multiple items – one table per entity type Denormalized: one item with flexible schema © 2020, Amazon Web Services, Inc. or its Affiliates. Ensuring data consistency on updates Example: add/remove shopping cart items 1. get cart => vread = Version 2. update cart: Use ConditionExpression IF Version = vread in DynamoDB add/remove cart items ++Version ELSE go back to Step 1. Optimistic concurrency control © 2020, Amazon Web Services, Inc. or its Affiliates. Updating cart: data consistency using OCC 1. Get the cart: GetItem 2. Update the cart: conditional PutItem (or UpdateItem) { "TableName": “Cart”, { "TableName": “Cart”, "Key": {“CartId”: {“N”: “2”}} "Item": { } “CartID”: {“N”: “2”}, “Version”: {“N”:”4”}, “CartItems”: {…} }, CART "ConditionExpression": “Version = :ver”, "ExpressionAttributeValues": {":ver": {“N”: “3”}} CartID:2, Version: 3, } CartItems: [ ü Use conditions to implement optimistic {ID: 2, Qty: 1}, concurrency control ensuring data consistency {ID: 5, Qty: 2}] ü Single-item operations are ACID ü GetItem call can be eventually consistent © 2020, Amazon Web Services, Inc. or its Affiliates. Yes, you can have strongly consistent read-after-write and concurrency control with DynamoDB © 2020, Amazon Web Services, Inc. or its Affiliates. One-to-one relationships or key-values • Use a table or GSI with a partition key • Use GetItem or BatchGetItem API Example: Given a user or email, get attributes Users table Partition key Attributes UserId = bob Email = [email protected], JoinDate = 2011-11-15 UserId = fred Email = [email protected], JoinDate = 2011-12-01 Users-Email-GSI Partition key Attributes Email = [email protected] UserId = bob, JoinDate = 2011-11-15 Email = [email protected] UserId = fred, JoinDate = 2011-12-01 © 2020, Amazon Web Services, Inc. or its Affiliates. One-to-many relationships or parent-children • Use a table or GSI with a partition and sort key • Use the Query API to get multiple items Example: Given a device, find all readings between epoch X, Y Device-measurements Part. key Sort key Attributes DeviceId = 1 epoch = 5513A97C Temperature = 30, pressure = 90 DeviceId = 1 epoch = 5513A9DB Temperature = 30, pressure = 90 © 2020, Amazon Web Services, Inc. or its Affiliates. Many-to-many relationships • Use a table and GSI with the partition and sort key elements switched • Use the Query API Example: Given a user, find all games. Or given a game, find all users. User-Games-Table Game-Users-GSI Part. key Sort key Part. key Sort key UserId = bob GameId = Game1
Recommended publications
  • Reliability and Security of Large Scale Data Storage in Cloud Computing C.W

    Reliability and Security of Large Scale Data Storage in Cloud Computing C.W

    This article is part of the Reliability Society 2010 Annual Technical Report Reliability and Security of Large Scale Data Storage in Cloud Computing C.W. Hsu ¹¹¹ C.W. Wang ²²² Shiuhpyng Shieh ³³³ Department of Computer Science Taiwan Information Security Center at National Chiao Tung University NCTU (TWISC@NCTU) Email: ¹[email protected] ³[email protected] ²[email protected] Abstract In this article, we will present new challenges to the large scale cloud computing, namely reliability and security. Recent progress in the research area will be briefly reviewed. It has been proved that it is impossible to satisfy consistency, availability, and partitioned-tolerance simultaneously. Tradeoff becomes crucial among these factors to choose a suitable data access model for a distributed storage system. In this article, new security issues will be addressed and potential solutions will be discussed. Introduction “Cloud Computing ”, a novel computing model for large-scale application, has attracted much attention from both academic and industry. Since 2006, Google Inc. Chief Executive Eric Schmidt introduced the term into industry, and related research had been carried out in recent years. Cloud computing provides scalable deployment and fine-grained management of services through efficient resource sharing mechanism (most of them are for hardware resources, such as VM). Convinced by the manner called “ pay-as-you-go ” [1][2], companies can lower the cost of equipment management including machine purchasing, human maintenance, data backup, etc. Many cloud services rapidly appear on the Internet, such as Amazon’s EC2, Microsoft’s Azure, Google’s Gmail, Facebook, and so on. However, the well-known definition of the term “Cloud Computing ” was first given by Prof.
  • Timeline 1994 July Company Incorporated 1995 July Amazon

    Timeline 1994 July Company Incorporated 1995 July Amazon

    Timeline 1994 July Company Incorporated 1995 July Amazon.com Sells First Book, “Fluid Concepts & Creative Analogies: Computer Models of the Fundamental Mechanisms of Thought” 1996 July Launches Amazon.com Associates Program 1997 May Announces IPO, Begins Trading on NASDAQ Under “AMZN” September Introduces 1-ClickTM Shopping November Opens Fulfillment Center in New Castle, Delaware 1998 February Launches Amazon.com Advantage Program April Acquires Internet Movie Database June Opens Music Store October Launches First International Sites, Amazon.co.uk (UK) and Amazon.de (Germany) November Opens DVD/Video Store 1999 January Opens Fulfillment Center in Fernley, Nevada March Launches Amazon.com Auctions April Opens Fulfillment Center in Coffeyville, Kansas May Opens Fulfillment Centers in Campbellsville and Lexington, Kentucky June Acquires Alexa Internet July Opens Consumer Electronics, and Toys & Games Stores September Launches zShops October Opens Customer Service Center in Tacoma, Washington Acquires Tool Crib of the North’s Online and Catalog Sales Division November Opens Home Improvement, Software, Video Games and Gift Ideas Stores December Jeff Bezos Named TIME Magazine “Person Of The Year” 2000 January Opens Customer Service Center in Huntington, West Virginia May Opens Kitchen Store August Announces Toys “R” Us Alliance Launches Amazon.fr (France) October Opens Camera & Photo Store November Launches Amazon.co.jp (Japan) Launches Marketplace Introduces First Free Super Saver Shipping Offer (Orders Over $100) 2001 April Announces Borders Group Alliance August Introduces In-Store Pick Up September Announces Target Stores Alliance October Introduces Look Inside The BookTM 2002 June Launches Amazon.ca (Canada) July Launches Amazon Web Services August Lowers Free Super Saver Shipping Threshold to $25 September Opens Office Products Store November Opens Apparel & Accessories Store 2003 April Announces National Basketball Association Alliance June Launches Amazon Services, Inc.
  • Amazon Dynamodb

    Amazon Dynamodb

    Dynamo Amazon DynamoDB Nicolas Travers Inspiré de Advait Deo Vertigo N. Travers ESILV : Dynamo Amazon DynamoDB – What is it ? • Fully managed nosql database service on AWS • Data model in the form of tables • Data stored in the form of items (name – value attributes) • Automatic scaling ▫ Provisioned throughput ▫ Storage scaling ▫ Distributed architecture • Easy Administration • Monitoring of tables using CloudWatch • Integration with EMR (Elastic MapReduce) ▫ Analyze data and store in S3 Vertigo N. Travers ESILV : Dynamo Amazon DynamoDB – What is it ? key=value key=value key=value key=value Table Item (64KB max) Attributes • Primary key (mandatory for every table) ▫ Hash or Hash + Range • Data model in the form of tables • Data stored in the form of items (name – value attributes) • Secondary Indexes for improved performance ▫ Local secondary index ▫ Global secondary index • Scalar data type (number, string etc) or multi-valued data type (sets) Vertigo N. Travers ESILV : Dynamo DynamoDB Architecture • True distributed architecture • Data is spread across hundreds of servers called storage nodes • Hundreds of servers form a cluster in the form of a “ring” • Client application can connect using one of the two approaches ▫ Routing using a load balancer ▫ Client-library that reflects Dynamo’s partitioning scheme and can determine the storage host to connect • Advantage of load balancer – no need for dynamo specific code in client application • Advantage of client-library – saves 1 network hop to load balancer • Synchronous replication is not achievable for high availability and scalability requirement at amazon • DynamoDB is designed to be “always writable” storage solution • Allows multiple versions of data on multiple storage nodes • Conflict resolution happens while reads and NOT during writes ▫ Syntactic conflict resolution ▫ Symantec conflict resolution Vertigo N.
  • [XIAY]⋙ Big Data Science & Analytics: a Hands-On Approach By

    [XIAY]⋙ Big Data Science & Analytics: a Hands-On Approach By

    Big Data Science & Analytics: A Hands-On Approach Arshdeep Bahga, Vijay Madisetti Click here if your download doesn"t start automatically Big Data Science & Analytics: A Hands-On Approach Arshdeep Bahga, Vijay Madisetti Big Data Science & Analytics: A Hands-On Approach Arshdeep Bahga, Vijay Madisetti We are living in the dawn of what has been termed as the "Fourth Industrial Revolution", which is marked through the emergence of "cyber-physical systems" where software interfaces seamlessly over networks with physical systems, such as sensors, smartphones, vehicles, power grids or buildings, to create a new world of Internet of Things (IoT). Data and information are fuel of this new age where powerful analytics algorithms burn this fuel to generate decisions that are expected to create a smarter and more efficient world for all of us to live in. This new area of technology has been defined as Big Data Science and Analytics, and the industrial and academic communities are realizing this as a competitive technology that can generate significant new wealth and opportunity. Big data is defined as collections of datasets whose volume, velocity or variety is so large that it is difficult to store, manage, process and analyze the data using traditional databases and data processing tools. Big data science and analytics deals with collection, storage, processing and analysis of massive-scale data. Industry surveys, by Gartner and e-Skills, for instance, predict that there will be over 2 million job openings for engineers and scientists trained in the area of data science and analytics alone, and that the job market is in this area is growing at a 150 percent year-over-year growth rate.
  • Amazon Web Services: Overview of Security Processes

    Amazon Web Services: Overview of Security Processes

    Amazon Web Services: Overview of Security Processes March 2020 For the latest technical content, see Best Practices for Security, Identity & Compliance https://aws.amazon.com/architecture/ security-identity-compliance Archived Notices Customers are responsible for making their own independent assessment of the information in this document. This document: (a) is for informational purposes only, (b) represents current AWS product offerings and practices, which are subject to change without notice, and (c) does not create any commitments or assurances from AWS and its affiliates, suppliers or licensors. AWS products or services are provided “as is” without warranties, representations, or conditions of any kind, whether express or implied. 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. © 2020 Amazon Web Services, Inc. or its affiliates. All rights reserved. Archived Contents Introduction .......................................................................................................................... 1 Shared Security Responsibility Model ................................................................................ 1 AWS Security Responsibilities ......................................................................................... 2 Customer Security Responsibilities ................................................................................. 2 AWS Global Infrastructure Security
  • Data Warehousing on AWS

    Data Warehousing on AWS

    Data Warehousing on AWS March 2016 Amazon Web Services – Data Warehousing on AWS March 2016 © 2016, 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 26 Amazon Web Services – Data Warehousing on AWS March 2016 Contents Abstract 4 Introduction 4 Modern Analytics and Data Warehousing Architecture 6 Analytics Architecture 6 Data Warehouse Technology Options 12 Row-Oriented Databases 12 Column-Oriented Databases 13 Massively Parallel Processing Architectures 15 Amazon Redshift Deep Dive 15 Performance 15 Durability and Availability 16 Scalability and Elasticity 16 Interfaces 17 Security 17 Cost Model 18 Ideal Usage Patterns 18 Anti-Patterns 19 Migrating to Amazon Redshift 20 One-Step Migration 20 Two-Step Migration 20 Tools for Database Migration 21 Designing Data Warehousing Workflows 21 Conclusion 24 Further Reading 25 Page 3 of 26 Amazon Web Services – Data Warehousing on AWS March 2016 Abstract Data engineers, data analysts, and developers in enterprises across the globe are looking to migrate data warehousing to the cloud to increase performance and lower costs.
  • Performance at Scale with Amazon Elasticache

    Performance at Scale with Amazon Elasticache

    Performance at Scale with Amazon ElastiCache July 2019 Notices Customers are responsible for making their own independent assessment of the information in this document. This document: (a) is for informational purposes only, (b) represents current AWS product offerings and practices, which are subject to change without notice, and (c) does not create any commitments or assurances from AWS and its affiliates, suppliers or licensors. AWS products or services are provided “as is” without warranties, representations, or conditions of any kind, whether express or implied. 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. © 2019 Amazon Web Services, Inc. or its affiliates. All rights reserved. Contents Introduction .......................................................................................................................... 1 ElastiCache Overview ......................................................................................................... 2 Alternatives to ElastiCache ................................................................................................. 2 Memcached vs. Redis ......................................................................................................... 3 ElastiCache for Memcached ............................................................................................... 5 Architecture with ElastiCache for Memcached ...............................................................
  • Amazon Documentdb Deep Dive

    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({
  • A Motion Is Requested to Authorize the Execution of a Contract for Amazon Business Procurement Services Through the U.S. Communities Government Purchasing Alliance

    A Motion Is Requested to Authorize the Execution of a Contract for Amazon Business Procurement Services Through the U.S. Communities Government Purchasing Alliance

    MOT 2019-8118 Page 1 of 98 VILLAGE OF DOWNERS GROVE Report for the Village Council Meeting 3/19/2019 SUBJECT: SUBMITTED BY: Authorization of a contract for Amazon Business procurement Judy Buttny services Finance Director SYNOPSIS A motion is requested to authorize the execution of a contract for Amazon Business procurement services through the U.S. Communities Government Purchasing Alliance. STRATEGIC PLAN ALIGNMENT The goals for 2017-2019 includes Steward of Financial Sustainability, and Exceptional, Continual Innovation. FISCAL IMPACT There is no cost to utilize Amazon Business procurement services through the U.S. Communities Government Purchasing Alliance. RECOMMENDATION Approval on the March 19, 2019 Consent Agenda. BACKGROUND U.S. Communities Government Purchasing Alliance is the largest public sector cooperative purchasing organization in the nation. All contracts are awarded by a governmental entity utilizing industry best practices, processes and procedures. The Village of Downers Grove has been a member of the U.S. Communities Government Purchasing Alliance since 2008. Through cooperative purchasing, the Village is able to take advantage of economy of scale and reduce the cost of goods and services. U.S. Communities has partnered with Amazon Services to offer local government agencies the ability to utilize Amazon Business for procurement services at no cost to U.S. Communities members. Amazon Business offers business-only prices on millions of products in a competitive digital market place and a multi-level approval workflow. Staff can efficiently find quotes and purchase products for the best possible price, and the multi-level approval workflow ensures this service is compliant with the Village’s competitive process for purchases under $7,000.
  • AWS Certified Developer – Associate (DVA-C01) Sample Exam Questions

    AWS Certified Developer – Associate (DVA-C01) Sample Exam Questions

    AWS Certified Developer – Associate (DVA-C01) Sample Exam Questions 1) A company is migrating a legacy application to Amazon EC2. The application uses a user name and password stored in the source code to connect to a MySQL database. The database will be migrated to an Amazon RDS for MySQL DB instance. As part of the migration, the company wants to implement a secure way to store and automatically rotate the database credentials. Which approach meets these requirements? A) Store the database credentials in environment variables in an Amazon Machine Image (AMI). Rotate the credentials by replacing the AMI. B) Store the database credentials in AWS Systems Manager Parameter Store. Configure Parameter Store to automatically rotate the credentials. C) Store the database credentials in environment variables on the EC2 instances. Rotate the credentials by relaunching the EC2 instances. D) Store the database credentials in AWS Secrets Manager. Configure Secrets Manager to automatically rotate the credentials. 2) A Developer is designing a web application that allows the users to post comments and receive near- real-time feedback. Which architectures meet these requirements? (Select TWO.) A) Create an AWS AppSync schema and corresponding APIs. Use an Amazon DynamoDB table as the data store. B) Create a WebSocket API in Amazon API Gateway. Use an AWS Lambda function as the backend and an Amazon DynamoDB table as the data store. C) Create an AWS Elastic Beanstalk application backed by an Amazon RDS database. Configure the application to allow long-lived TCP/IP sockets. D) Create a GraphQL endpoint in Amazon API Gateway. Use an Amazon DynamoDB table as the data store.
  • A Serverless Journey: Under the Hood of AWS Lambda

    A Serverless Journey: Under the Hood of AWS Lambda

    S V S 4 0 5 - R A Serverless Journey: Under the Hood of AWS Lambda Holly Mesrobian Marc Brooker Director of Engineering Senior Principal Engineer Amazon AWS Lambda Amazon AWS Serverless Amazon Web Services Amazon Web Services © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. SERVERLESS AT SCALE IS THE NEW NORM processes 4,000 requests executes 16 million per second requests a month processes half a trillion validations of stock trades daily ingests, analyzes and processes tens of stores 17+ petabytes of billions of data data per season points monthly API traffic to register and license more than 47 million driver records in Great Britain, © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Load Balancing Scaling Up and Down Handling Failures Predictable Low Latency AWS Lambda Handles Event Processing Stream Processing Predictable Performance Innovations in Isolation © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS Cloud Region Availability Zone 1 Worker Mgr Worker Claim Worker Invoke Placement Front End Invoke Reserve Sandbox Worker Mgr Init Lambda customer Worker (New Function or Scaling Up) Invoke Front End Worker Availability Zone 2 AWS Cloud Region Availability Zone 1 Worker Mgr Worker Invoke Front End Invoke Reserve Sandbox Lambda customer Worker Mgr Worker (Existing Worker, Existing Sandbox) Invoke Front End Worker Availability Zone 2 Poller Consumes events and ensures they are processed State Manager or Stream Tracker Handles scaling by managing Pollers and event or stream source resources Leasing Service Assigns Pollers to work on a specific event or streaming source © 2019, Amazon Web Services, Inc.
  • The Complete Guide to Social Media from the Social Media Guys

    The Complete Guide to Social Media from the Social Media Guys

    The Complete Guide to Social Media From The Social Media Guys PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Mon, 08 Nov 2010 19:01:07 UTC Contents Articles Social media 1 Social web 6 Social media measurement 8 Social media marketing 9 Social media optimization 11 Social network service 12 Digg 24 Facebook 33 LinkedIn 48 MySpace 52 Newsvine 70 Reddit 74 StumbleUpon 80 Twitter 84 YouTube 98 XING 112 References Article Sources and Contributors 115 Image Sources, Licenses and Contributors 123 Article Licenses License 125 Social media 1 Social media Social media are media for social interaction, using highly accessible and scalable publishing techniques. Social media uses web-based technologies to turn communication into interactive dialogues. Andreas Kaplan and Michael Haenlein define social media as "a group of Internet-based applications that build on the ideological and technological foundations of Web 2.0, which allows the creation and exchange of user-generated content."[1] Businesses also refer to social media as consumer-generated media (CGM). Social media utilization is believed to be a driving force in defining the current time period as the Attention Age. A common thread running through all definitions of social media is a blending of technology and social interaction for the co-creation of value. Distinction from industrial media People gain information, education, news, etc., by electronic media and print media. Social media are distinct from industrial or traditional media, such as newspapers, television, and film. They are relatively inexpensive and accessible to enable anyone (even private individuals) to publish or access information, compared to industrial media, which generally require significant resources to publish information.