亚马逊 代闻 - Cloud Native 架构的演进之路

化念雁

2017/12/18 发布于 技术 分类

ArchSummit全球架构师峰会是InfoQ中国团队推出的面向高端技术管理者、架构师的技术大会,参会者中超过50%拥有8年以上的工作经验。 ArchSummit秉承“实践第一、案例为主”的原则,展示新技术在行业应用中的最新实践,技术在企业转型中的加速作用,帮助企业技术管理者、CTO、架构师做好技术选型、技术团队组建与管理,并确立技术对于产品和业务的关键作用。

文字内容
1. Cloud Native 架构的演进之路 代闻 亚马逊AWS解决方案架构团队 技术经理
5. 什么是 Cloud Native?
6. 什么是 Cloud Native? Answer by CNCF Cloud native computing uses an open source software stack to be: 1. Containerized. Each part (applications, processes, etc) is packaged in its own container. This facilitates reproducibility, transparency, and resource isolation. 2. Dynamically orchestrated. Containers are actively scheduled and managed to optimize resource utilization. 3. Microservices oriented. Applications are segmented into microservices. This significantly increases the overall agility and maintainability of applications. https://www.cncf.io/about/faq/
7. 什么是 Cloud Native? Answer by Adrian Cockcroft, CNCF Board Member, AWS VP of Cloud Architecture, Former Cloud Architect of Netflix Cloud native architectures take full advantage of on-demand delivery, global deployment, elasticity, and higher-level services. They enable huge improvements in developer productivity, business agility, scalability, availability, utilization, and cost savings. https://medium.com/@adrianco/cloud-native-computing-5f0f41a982bf
8. Cloud Native 架构的演进 Microservices Architecture VM Container Serverless Cloud Services DevOps
10. Netflix Architecture before 2009
11. 2010年开始向云上迁移
12. 2012年多区域部署
13. 2013 – 2014 完成多活
14. Netflix Cloud Native 架构关键点
15. Netflix All-In AWS的微服务架构 •  Netflix OSS: http://netflix.github.io/ 参考: https://www.infoq.com/presentations/netflix-chaos-microservices
16. Microservice 失效测试与恢复
18. ChAP: Chaos Automation Platform
21. 微服务典型单元 Eureka:服务发现 Hystrix:断路器(Lib)
22. 数据库的高可用与最终一致性 Cassandra Cassandra
23. Cache的高可用与最终一致 EVCache
24. Cache的高可用与最终一致 EVCache
25. Cache的高可用与最终一致性 EVCache
26. DNS
27. DNS 控制- Denominator
28. Netflix A/A 架构关键点 •  Services must be stateless — all data / state replication needs to handled in data tier. •  They must access any resource locally in-Region. This includes resources like S3, SQS, etc. This means several applications that are publishing data into an S3 bucket, now have to publish the same data into multiple regional S3 buckets. •  there should not be any cross-regional calls on user’s call path. Data replication should be asynchronous. https://medium.com/netflix-techblog/active-active-for-multi-regional-resiliency-c47719f6685b
29. Netflix OSS •  https://netflix.github.io/
30. Time to re:Invent the Architecture …
31. 不断发展的云服务 为新用户带来的后发优势
32. 容器服务
33. Netflix使用Amazon ECS部署容器集群
34. NoSQL: DynamoDB and DynamoDB Stream
35. NoSQL A/A: DynamoDB Global Table
37. RDBMS: Aurora
38. RDBMS A/A: Aurora Multi-Master
39. Serverless
40. 事件驱动
43. Cloud Native开发测试环境
44. Containerized, Dynamically Orchestrated, Microservices Oriented. On-Demand Delivery, Global Deployment, Elasticity, and Higher-Level Services.