数据工程和技术分会场Cloud+Native+Applications.docxVIP

Cloud Native Applications 主讲人：Capital One 首席工程师 Kevin Hoffman Agenda Define Cloud Native Cloud Native practices and the “15 factors” From Monoliths to the Cloud QA What is Cloud Native? Contract between application and infrastructure Designed to scale elastically and horizontally No host dependencies Application conforms to the “12 (or 15) factors” Container-based* Team Discipline 云道 Structure around rapid, continuous delivery Embrace agility Embrace the cloud Adopt practices aimed at thriving on cloud platforms The Way of the Cloud 云道 Favor Simplicity Test First, Test Everything Release Early, Release Often Automate Everything Build Ecosystems, not Monoliths 15 Factors of Cloud Native 十五个因素 Based on Heroku’s original “12 factor” list (12) Characteristics of a cloud native application Some easier to adopt than others Adopting all factors pays huge dividends One codebase, One App 第一 Single version-controlled codebase, many deploys Multiple apps should not share code Microservices need separate release schedules Upgrade, deploy one without impacting others Tie build and deploy pipelines to single codebase API First 第二 Service ecosystem requires a contract Public API Multiple teams on different schedules Code to contract/API, not code dependencies Use well-documented contract standards Protobuf IDL, Swagger, Apiary, etc API First != REST First RPC can be more appropriate in some situations Dependency Management 第三 Explicitly declare dependencies Include all dependencies with app release Create immutable build artifact (e.g. docker image) Rely on smallest docker image Base on scratch if possible App cannot rely on host for system tools or libraries Design, Build, Release, Run 第四 Design part of iterative cycle Agile doesn’t mean random or undesigned Mature CI/CD pipeline and teams Design to production in days not months Build creates immutable artifact Release automatically deploys to environment Environment contains config, not release artifact Configuration, Credentia