DynamoDB High Availability
Backup and Restore
Point in Time Recovery
The course is part of these learning paths
This course explores Amazon Web Service's DynamoDB and teaches you how to architect DynamoDB setups—with an emphasis on high availability—ensuring that your internet-scale applications are always available. The course begins by looking at the various option offered by DynamoDB, before moving onto on-demand backup and restore, and rounding off by looking at point in time recovery. In each section, there is a real-world demonstration from the AWS platform which walks you through the topics covered.
If you have any feedback, queries, or suggestions relating to this course, please contact us at firstname.lastname@example.org.
- Understand how to provision and configure DynamoDB in a manner that ensures it is highly available and able to serve all read and write requests to it.
This course has been created for those who are responsible for architecting DynamoDB setups.
To get the most from this course you should be familiar with basic NoSQL concepts, and DynamoDb concepts such as Tables, Items, and Attributes. Consider watching our dedicated “Working with Amazon DynamoDB” course and/or review the “10 Things You Should Know” about DynamoDB blog post, before taking this course.
The following GitHub repository is referenced within this course:
Point In Time Recovery or PITR - is an enhanced version of the on-demand backup and restore feature, providing you with the ability to perform point in time recoveries. This feature is extremely handy in situations when you’re modifying data and want a safety net in place for the situation where your data modifications didn’t result in the way they should have. With PITR in place, you can simply restore back to a specific time. PITR takes the burden away of having to plan backup schedules, etc.
Point In Time Recovery operates at the table level, and when enabled provides you with the ability to perform a point in time recovery for any time between the current time and the last 35 days. This feature needs to be enabled as it is disabled by default. Once enabled you can request a recovery by specifying a date and time with second precision or granularity. The restoration will always be performed into a new table - of which you specify the new table name at time of restoration request. Table restoration can be performed in the same region as the original table, or into a different region altogether.
About the Author
Jeremy is the DevOps Content Lead at Cloud Academy where he specializes in developing technical training documentation for DevOps.
He has a strong background in software engineering, and has been coding with various languages, frameworks, and systems for the past 20+ years. In recent times, Jeremy has been focused on DevOps, Cloud, Security, and Machine Learning.
Jeremy holds professional certifications for both the AWS and GCP cloud platforms.