Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
The Road Map to
Becoming a
DevOps
Professional
A Short History
Different Perspectives
Let’s Forget About
Definitions
DevOps Engineers, DevOps
Teams
● 16% identified themselves as working in DevOps teams in 2014
● 19% in 2015
● 22% in 2016
State of DevOps
A Catalyst For Change
● Planting The 1st Seed
● Bootstrapping DevOps
● Costs / Risks
The Full Stack Developer
● Transformation of all teams can come with costs and risks
● A Developer cannot do everything
Why ?
Skill #1:
Global/Strategic
Thinking &
Communication Skills
Skill #2: Code
Skill #3: Quality
Assurance
Skill #4: Security
Skill #5: Networking
Skill #6: Databases
Software Everywhere
With Great Power
Comes Great
Responsibility
Being More Productive
DevOps Should Be An
Evidence
Different Perspectives
Standardization
Patterns
● Successful DevOps Implementations (Netflix)
● The 12 Factor App (Heroku)
● The 13 Factor App (Mesosphere)
● Clo...
Products, Not Projects
Features, Not Releases
Business-IT Alignment
Core Value Focus
Re-usability
Technology Agnosticism
A...
20 Patterns
15 Factors
●
Embrace the DevOps Culture
●
Environment Isolations & Dev/Prod Parity
●
Anything as a Service
●
Use Cloud Com...
●
Yesterday’s DevOps =/= Today’s DevOps of Today =/= Tomorrow’s DevOps
●
DevOps engineer role and DevOps teams are becomin...
Thanks !
Aymen El Amri
@eon01
aymen@eralabs.io
Join DevOpsLinks: www.devopslinks.com
The Roadmap to Becoming a DevOps Professional
The Roadmap to Becoming a DevOps Professional
The Roadmap to Becoming a DevOps Professional
The Roadmap to Becoming a DevOps Professional
The Roadmap to Becoming a DevOps Professional
The Roadmap to Becoming a DevOps Professional
The Roadmap to Becoming a DevOps Professional
The Roadmap to Becoming a DevOps Professional
The Roadmap to Becoming a DevOps Professional
Upcoming SlideShare
Loading in …5
×

The Roadmap to Becoming a DevOps Professional

483 views

Published on

Even if there is one common definition for "DevOps", it should be re-defined every few months since DevOps ecosystem is changing fast.

I am trying through this presentation to give my opinion about the DevOps engineer position, DevOps teams & a standardization framework for the DevOps success.

Published in: Technology
  • Be the first to comment

The Roadmap to Becoming a DevOps Professional

  1. 1. The Road Map to Becoming a DevOps Professional
  2. 2. A Short History
  3. 3. Different Perspectives
  4. 4. Let’s Forget About Definitions
  5. 5. DevOps Engineers, DevOps Teams
  6. 6. ● 16% identified themselves as working in DevOps teams in 2014 ● 19% in 2015 ● 22% in 2016 State of DevOps
  7. 7. A Catalyst For Change ● Planting The 1st Seed ● Bootstrapping DevOps ● Costs / Risks
  8. 8. The Full Stack Developer
  9. 9. ● Transformation of all teams can come with costs and risks ● A Developer cannot do everything Why ?
  10. 10. Skill #1: Global/Strategic Thinking & Communication Skills
  11. 11. Skill #2: Code
  12. 12. Skill #3: Quality Assurance
  13. 13. Skill #4: Security
  14. 14. Skill #5: Networking
  15. 15. Skill #6: Databases
  16. 16. Software Everywhere
  17. 17. With Great Power Comes Great Responsibility
  18. 18. Being More Productive
  19. 19. DevOps Should Be An Evidence
  20. 20. Different Perspectives
  21. 21. Standardization
  22. 22. Patterns ● Successful DevOps Implementations (Netflix) ● The 12 Factor App (Heroku) ● The 13 Factor App (Mesosphere) ● Cloud Native Computing Foundation ● Web-scale (Google, Amazon ..)
  23. 23. 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
  24. 24. 20 Patterns
  25. 25. 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
  26. 26. ● 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
  27. 27. Thanks ! Aymen El Amri @eon01 aymen@eralabs.io Join DevOpsLinks: www.devopslinks.com

×