
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 3 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build blog article learn world project boat download windows security lookup free performance javascript technical network control beautiful support london tools course file research purchase library programming image youtube example php construction html opensource quality install community computer profile feature power browser music platform mobile user process work database share manage hardware professional buy industry internet dance advice installation developer 3d search material access customer camera travel test standard review documentation css money engineering develop webdesign engine device photography digital api speed source program management phone discussion question event client story simple water marketing app yacht content setup package fast idea interface account communication cheap compare script study market live easy google resource operation startup monitor training
Tag selected: rds.
Looking up rds tag. Showing 3 results. Clear
Saved by uncleflo on July 24th, 2019.
Many customers want a disaster recovery environment, and they want to use this environment daily and know that it's in sync with and can support a production workload. This leads them to an active-active architecture. In other cases, users like Netflix and Lyft are distributed over large geographies. In these cases, multi-region active-active deployments are not optional. Designing these architectures is more complicated than it appears, as data being generated at one end needs to be synced with data at the other end. There are also consistency issues to consider. One needs to make trade-off decisions on cost, performance, and consistency. Further complicating matters is the variety of data stores used in the architecture results in a variety replication methods. In this session, we explore how to design an active-active multi-region architecture using AWS services, including Amazon Route 53, Amazon RDS multi-region replication, AWS DMS, and Amazon DynamoDB Streams. We discuss the challenges, trade-offs, and solutions.
disaster aws recovery environment day sync production workload architecture netflix geography region deployment design consistent complication performance store replication method session amazon route data rds challenge trade solution multi-region administration youtube movie guide
Saved by uncleflo on June 23rd, 2019.
A lot of RDS's documentation about read replicas contains a magical step along the lines of "direct database traffic to the new master." For instance, their instructions on implementing failure recovery say: This talk about directing traffic glosses over what is actually a complicated step, though. If I were using EC2 instances to host my database, I could give them elastic IPs, use the public DNS address of the instance to address it (which resolves to its private IP from inside AWS), and then instantly swap my entire stack to the read replica by reassigning the elastic IP (and thus simultaneously reassigning the public DNS). I used this method happily back in the days when RDS was considered straightforwardly inferior to rolling your own database instance on EC2 by many DBAs. RDS instances still cannot have elastic IPs, though, so I cannot use this particular trick to magically redirect all my database traffic to a new instance when using RDS.
downtime unscheduled overflow fault deploy database answer server documentation automatic failover address reassign method rds inferior complicated disaster recovery instance host aurora instruction replication switch administration cloud aws howto discussion question
Saved by uncleflo on June 23rd, 2019.
Lab-2: Below is the steps that we had followed to setup Route 53 failover and achive disaster recovery of Application and RDS database. We will examine the Primary Region 1 and what to do, the Secondary Region 2 and the steps there, Failover route 53 from one region to another and set it up, and Test your failover.
test administration failover disaster recover route application rds database region examine follow setup replication solution amazon read video youtube watch howto explanation development
No further bookmarks found.