Architecting For Scale • Lee Atchison & Ken Gavranovic

Testing

Architecting For Scale: Learn how to identify and prioritize risks, test and deploy systems, and plan for disaster recovery and chaos engineering to scale your systems efficiently.

Key takeaways

Conference talk on architecting for scale, with key takeaways on:
- Risk matrix: a tool for identifying and prioritizing risks, and making informed decisions
- Importance of testing, including game days and chaotic production environments
- Continuous integration and deployment (CI/CD) is essential for scaling systems
- Disaster recovery planning and testing is crucial for system availability
- Microservices and service-level objectives (SLOs) require careful planning and implementation
- Disaster recovery plans should be tested and rehearsed to ensure effectiveness
- Chaos engineering is important for testing systems in production to identify flaws
- Test suites and risk matrices are essential for identifying and prioritizing risks
- Chaos engineering and game days are important for testing systems in production to identify flaws
- Importance of documentation and communication with stakeholders
- Importance of planning and investment in processes and procedures
Major trends and challenges:
- Migration to cloud and microservices
- Importance of CI/CD and disaster recovery planning
- Need for chaos engineering and game days
- Importance of communication and documentation with stakeholders
Recommendations:
- Plan and invest in processes and procedures
- Use risk matrices and test suites to identify and prioritize risks
- Perform chaos engineering and game days
- Emphasize importance of documentation and communication with stakeholders
Important tools and resources:
- Risk matrix
- Test suites
- CI/CD
- Chaos engineering
- Game days
- Disaster recovery planning and testing
Books and publications mentioned:
- “Architecting for Scale”
- “GoTo Podcast”
- “O’Reilly” articles and books

Architecting For Scale • Lee Atchison & Ken Gavranovic

More talks