{"id":929,"date":"2010-05-18T00:00:00","date_gmt":"2010-05-18T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2010\/05\/18\/amazon-cloud-based-database-gains-high-availability-feature\/"},"modified":"2021-12-30T11:38:25","modified_gmt":"2021-12-30T11:38:25","slug":"amazon-cloud-based-database-gains-high-availability-feature","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2010\/05\/18\/amazon-cloud-based-database-gains-high-availability-feature\/","title":{"rendered":"Amazon cloud-based database gains high-availability feature"},"content":{"rendered":"<p>Amazon Web Services has added a new high-availability feature called Multi-Availability Zone (Multi-AZ) to its cloud-based Relational Database Service (RDS), the company said on Tuesday.  The addition of Multi-AZ provides better database availability by automatically configuring a standby copy of the database, which is stored in a different physical location from the original in Amazon&#8217;s cloud.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The addition of Multi-AZ provides better database availability by automatically configuring a standby copy of the database, which is stored in a different physical location from the original in Amazon&#8217;s cloud.<\/p>\n<p>From start to finish, the failover between the two databases typically completes within five minutes, according to Amazon.<\/p>\n<p>Amazon RDS is based on MySQL 5.1 and is still in beta.<\/p>\n<p>Amazon is also working on a second feature that will replicate data to improve scalability by using multiple database instances at the same time.<\/p>\n<p>http:\/\/www.infoworld.com\/d\/cloud-computing\/amazon-cloud-based-database-gains-high-availability-feature-213?source=rss_infoworld_news<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-929","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/929","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=929"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/929\/revisions"}],"predecessor-version":[{"id":3416,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/929\/revisions\/3416"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=929"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=929"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=929"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}