AWS Perú Meetup - Arquitecting for HA by Raul Hugo
Download as PPTX, PDF0 likes266 views
The document discusses high availability (HA) system design within the context of AWS, focusing on key architectural patterns and strategies. It outlines aspects like scalability, automation, loose coupling, service-oriented architectures, and caching methods to ensure system reliability and performance. Additionally, it highlights the importance of a well-architected design for reducing rework, enhancing user satisfaction, and achieving high availability metrics.
AWS Perú Meetup - Arquitecting for HA by Raul Hugo
- 1. @raulhugo Comunidad de AWS Perú Enero 2016 © 2017, AWS Peru or its Affiliates. All rights reserved. Introducing Architecting for HA AWS User Group Peru AWSPeru: Meetup
- 2. About Raul Hugo Just another *nix guy and Cslt-Sys Engineer at Verizon
- 3. What’s High Availabilty Characteristic of a system. Aims to ensure uptime and agree level of performance, for a higher than normal period.
- 4. How can I built a High Available System? With cloud Following Design Patterns and Architectural options available in AWS
- 5. Scalability 1. Vertical 2. Horizontal 1. Stateless Application 2. Stateless Components 3. Statefull Components (Databases) 4. Distribute Processing
- 6. Disposable Resources instead Fixed Servers 1. Bootstraping 2. Golden Images 3. Infraestructure As Code
- 7. Automation 1. Auto scaling 2. Cloudwatch alarms. 3. Cloudwatch events 4. Lambda Scheduled Events
- 8. Loose Coupling 1. Reduces interdependences. 2. Should not cascade. 3. Well defined intefaces. 4. RESTful APIs 5. Amazon Api Gateway. 6. Service discovery. Like Netflix Eureka 7. ELB, ALB 8. Asynchronous Integration 9. Graceful Failure
- 9. Service not Servers 1. Managed Services 2. Serverless Architectures (AWS Lambda)
- 10. Caching 1. App Data Caching (Elastic Cache) 2. Edge Caching (Cloudfront)
- 11. And how about Databases? 1. Lets talk about it the next Meetup.
- 12. Why this is important to me? Well architected design helps to: 1. Avoid rework. 1. Make changes on the app when an architectural change is needed. 2. Easy migrations. 3. Easy deployments 4. Don’t be worried about maintenance. 2. Impacts on the revenue. 1. Happy users 2. Almost %99.xxxx of availability.
- 13. Questions
- 14. Thank You