The document discusses the evolving landscape of DevOps, highlighting the increasing integration of development and operations teams to enhance software delivery efficiency. It emphasizes the importance of culture, continuous delivery, and managing software from development to production. The author refers to resources like 'The Phoenix Project' and 'The DevOps Handbook' for further reading.

1. DevOpsBEHIND THE SCENES
@mateusprado

2. $ whoami
• Software Engineer
• Co-founder @ CodeOps
• C6 Bank #TheNextBigFin
• “keep it simple”
• <3 API’s, concurrency, parallelism
• Automation and distributed systems
• Airplanes

3. Agenda
• Why DevOps?
• Industrial [E]volution
• Dev and Ops are changing
• Take care
• It's all about Culture

4. Our work is changing

8. Pattern
Speed To Market

9. In the not-so-distant
past…

10. To build a Software Company
• Cabinets and racks
• Servers
• Redundant power systems
• Manage a lot of hardware
• And one team…

11. Ops

12. To build a Software Company[2]
• and another one…

13. Devs

14. – Dev and Ops talking about deploy
Dev - “Hi, can you deploy the application? I sent you the
file by email”
So so far away…

15. – Dev and Ops talking about deploy
Ops - “Okay, I've restarted the service but it's returning an
error…”
So so far away…

16. – Dev and Ops talking about deploy
Dev - “strange, here it’s working, take a look:
http://localhost:8080/login
So so far away…

18. Number of servers
increases

20. Snowflake servers

21. Releases become
slow

22. Changes are painful

23. Bugs increases

24. Outages and downtime
become more frequent.

25. Release cadence to
once per week…

26. Once per month…

27. Once every six
months.

29. A profound shift is
taking place

30. Moving to the Cloud

31. Ops teams are spending
all their time working on
software.

32. Racking Servers and Plugging in network cables
Writing code.
sysadmins

34. Ready?

35. Fit?

38. Softwares need to be
managed…

39. Need to own.

43. Softwares need to be
tested…

44. Need to be scalable

45. Ops teams write code, now.
CODE.

46. LoC >> Software

47. Softwares need to be
tested…

48. Q.A and Ops don’t
match.

49. Ready?

50. Fit?

51. DevOps isn’t the name
of a team or a job title.

52. It’s a set of process, ideas
and tools.

53. The goal of DevOps is to make
software delivery more efficient.

55. Software isn’t done when the code
is working on your computer.

57. It’s not done when
the tests pass.

58. Software isn’t done until you
deliver it to the user.

59. • solve real problems
• measure everything
• do not wait for the next problem
• done != production ready
• sense, no luck

60. To help you with DevOps
The Phoenix Project - http://a.co/fxbJF4U
The DevOps Handbook - http://a.co/7miIjOQ
Continuous Delivery - http://a.co/8oQVExt
Site Reliability Engineering: How Google Runs
Production Systems - http://a.co/03271Wb
“semana devops”
Inter DevOps Conf
@mateusprado
mateus@mateusprado.com