The Roadmap to Becoming a DevOps Professional
3 likes855 views
The document outlines the evolution and importance of DevOps, highlighting the increasing identification of professionals in DevOps roles from 2014 to 2016. It emphasizes essential skills for DevOps engineers, successful implementations, and key patterns that facilitate DevOps culture and best practices. The conclusion stresses the need for collaboration, multidisciplinary approaches, and standards across teams to address challenges in the DevOps landscape.
The Roadmap to Becoming a DevOps Professional
- 1. The Road Map to Becoming a DevOps Professional
- 9. ● 16% identified themselves as working in DevOps teams in 2014 ● 19% in 2015 ● 22% in 2016 State of DevOps
- 11. A Catalyst For Change ● Planting The 1st Seed ● Bootstrapping DevOps ● Costs / Risks
- 12. The Full Stack Developer
- 13. ● Transformation of all teams can come with costs and risks ● A Developer cannot do everything Why ?
- 15. Skill #2: Code
- 26. With Great Power Comes Great Responsibility
- 28. DevOps Should Be An Evidence
- 30. Standardization
- 31. Patterns ● Successful DevOps Implementations (Netflix) ● The 12 Factor App (Heroku) ● The 13 Factor App (Mesosphere) ● Cloud Native Computing Foundation ● Web-scale (Google, Amazon ..)
- 32. Products, Not Projects Features, Not Releases Business-IT Alignment Core Value Focus Re-usability Technology Agnosticism Abstraction Simplicity Portability Cost Speed Self-service On-demand Resources Scalability Elasticity Reactiveness Resiliency Interoperability Security Traceability 20 Patterns
- 33. 20 Patterns
- 34. 15 Factors ● Embrace the DevOps Culture ● Environment Isolations & Dev/Prod Parity ● Anything as a Service ● Use Cloud Computing ● Use Containers ● Automate Everything ● Build Microservices ● Create Business Capability Teams & Deploy Business Services ● Build API-First Products ● Explicitly Isolate & Define Software Dependency ● Externalize Configurations ● Create Immutable Infrastructures & Artifacts ● Stream Logs ● Build Light & Business-Oriented Services ● Use Health Checks & Create Self-healing System
- 35. ● Yesterday’s DevOps =/= Today’s DevOps of Today =/= Tomorrow’s DevOps ● DevOps engineer role and DevOps teams are becoming common in high and meduim-performing IT organizations ● The first challenge of a DevOps engineer/team is not falling in the silo model ● The second challenge is being multidisciplinary ● Don’t try to find the best definition for DevOps, focus on problems and solutions instead ● Standards are the best way to keep common goals between teams and unify different perspectives and approaches Conclusion
- 36. Thanks ! Aymen El Amri @eon01 aymen@eralabs.io Join DevOpsLinks: www.devopslinks.com