My short Devops fundamentals talk


Serhat Can

April 23, 2020


  1. 3.

    @srhtcn FACT: Did you know that since last October, you

    can in fact find DevOps engineers with 10 years of experience?
  2. 6.

    @srhtcn 2009: “Devopsdays Ghent” • “10+ Deploys a Day: Dev

    and Ops Cooperation at Flickr” by John Allspaw and Paul Hammond • Developers and System Administrators get together in Ghent • #Devopsdays hashtag shortens to #DevOps
  3. 7.

    • Whenever it starts is the right time • Software

    has become the single most important thing for any business • Downtime was no longer acceptable - changing user needs • Delivering software faster than competition became a competitive advantage • Agile is in the foundation of DevOps • Iterative approach, collaboration, customer feedback, small - rapid releases WHY DOES THE HISTORY MATTER?
  4. 10.

    A culture where people, regardless of title or background, work

    together to imagine, develop, deploy and operate a system. DEVOPS DEFINITIONS I LIKE Ken Mugrage
  5. 11.

    DevOps is the combination of cultural philosophies, practices, and tools

    that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. DEVOPS DEFINITIONS I LIKE Amazon Web Services
  6. 13.
  7. 14.

    Let me explain. YOU SAY DEVOPS IS NOT A JOB

    TITLE OR SOMETHING WE DO? Companies have their own realities. Factors like legacy apps, company size, sector or even engineer’s backgrounds affect what DevOps is for them.
  8. 15.

    @srhtcn AMAZON’S WAY OF DEVOPS Two pizza teams Full ownership

    Full accountability
  9. 17.

    @srhtcn OPSGENIE’S WAY OF DEVOPS: SRE Developers have full ownership:

    they test, ship, log, monitor and get alerted SRE team educates and enables developers on the way to prod
  10. 18.

    @srhtcn WHAT IS DEVOPS 1. Developers take ownership: they ship,

    log, monitor and respond to incidents 2.Turn traditional ops into an engineering role. 3.Threat services like products. 4.Design and architect to foster collaboration and ownership.
  11. 19.

    @srhtcn WHAT IS NOT DEVOPS Using Kubernetes is not doing

    Devops Naming your Ops to DevOps or SRE is not doing Devops Building delivery pipeline, using Jenkins is not doing Devops …
  12. 20.

    @srhtcn Recommended books and resources • The DevOps Handbook •

    The Phoenix project & The Unicorn Project • DevOps for dummies • Accelerate • Google’s SRE books • Incident management for operations