Downloaded 58 times
Uploaded byChanny Yun
Chaos Engineering 시작하기 - 윤석찬 (AWS 테크에반젤리스트) :: 한국 카오스엔지니어링 밋업
The document outlines Netflix's transition from a monolithic architecture to a microservices approach, initiated post a datacenter failure in 2008, culminating in a complete migration to the cloud by 2015. It discusses the implementation of chaos engineering principles to manage system reliability, utilizing tools like Chaos Monkey to simulate failures and ensure robustness. Key aspects include the significant increase in customer interactions and metrics handled by Netflix's infrastructure, emphasizing the scale of its operations.
More Related Content
Similar to Chaos Engineering 시작하기 - 윤석찬 (AWS 테크에반젤리스트) :: 한국 카오스엔지니어링 밋업
![[다운로드] 한국 웹20주년 기념 소책자](https://cdn.slidesharecdn.com/ss_thumbnails/www20krbook-171013042831-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Chaos Engineering 시작하기 - 윤석찬 (AWS 테크에반젤리스트) :: 한국 카오스엔지니어링 밋업
- 1. / . 10/ 21 /7 2 118 2
- 2.
- 3. (c) Josh Evans,Mastering Chaos A Netflix Guide to Microservices, QCon SF 2016 Netflix DVD Data Center - 2000 Linux Host Apache Tomcat Javaweb STORE LoadBalancer BILLING HTTP JDBC DB Link HTTP/S Monolithic code base Monolithic database Tightly coupled architecture
- 4. 100s of microservices 1000sof daily production changes 10,000s of instances 100,000s of customer interactions per minute 1,000,000s of customers 1,000,000,000s of metrics 10,000,000,000 hours of streamed (c) Dave Hahn, A Day in the Life of a Netflix Engineer Using 37% of the Internet, re:Invent 2015 10s of operations engineers No Datacenter • 2008 – Datacenter failure (must be a better way) • 2009 – Cloud effort starts • 2010 – The first devices are talking to Netflix in the cloud (US-EAST-1) • 2011 – EU-WEST-1 • 2013 – US-WEST-2 (active/active) • 2015 – Migration Complete
- 5. Edge ELB Zuul NCCP API Middle Tier &Platform Product • Bucket testing • Subscriber • Recommendations Platform • Routing • Configuration • Crypto Persistence • Cache • Database (c) Josh Evans, Mastering Chaos A Netflix Guide to Microservices, QCon SF 2016
- 6. E • ( • (/ F o Sv c dB xe n B l F +/ +/ k F D y u c d • +/ / ( v n L Cp r : v b Cp e t s R ic E • ( • ( , / / / c i c c as • ) • ) / ) c c d d B e / u y m
- 7. (c) Ruslan Meshenberg,From Asgard to Zuul, re:Invent 2014
- 8. ( ) Chaos Monkey https://github.com/ne tflix/chaosmonkey InstanceFail? Chaos Gorilla Zone Fail? Chaos Kong Region Fail? .
- 9. - , ,-, , , A , , , A , , , , , , , A , , & , (c) Josh Evans, Mastering Chaos A Netflix Guide to Microservices, QCon SF 2016
- 10. http://channy.creation.net/blog/netflix-principles-of-chaos-engineering s ). 13,,2 h ea o g n E ‘ 4 n re i e o ’ C n ( n
- 11.
- 12. Presented by AdrianCockcroft, VP of Cloud Strategy, AWS
- 13. ( ) (()
- 14. No single point offailure ReplicatedDistributed Automated Cloud
- 17.
- 20.
- 21.
- 23.
- 24.
- 26.
- 27. Chaos Engineering Team Game days Simian Army FailureInjection ChAP Gremlin
- 28.
- 29.
- 30. :) : (. ( : R S l i S l h ? gE C ? Oa e a nD b ? Q :) -
- 31.