We make software and when we go into production (and not only) we need an artifact to deploy. The artifacts have been evolved more or less parallel to the culture of devops, their changes have not been random but the result of practices and mentality that have progressed. From the zipper to the docker image, from a url to a docker-compose, passing through many other nuances. Let's retrace this path and see how the culture devops has supported and pushed this evolution!

1. Artifacts
evolution
Marco Fracassi
@fracassi_marco

2. 2
Why this talk?

3. 3
How many devs?
How many ops?

4. 4
DevOps Heroes
#DOH18

5. Be lazy

6. What is an
artifact?

7. Opera (sia materiale che intellettuale) che
deriva da un processo trasformativo
intenzionale da parte dell'uomo
-- wikipedia --

8. Floppy disks era
(1990)

9. One time deploy

10. Multiple artifacts

11. Who are the Ops?

12. Distance between
devs and ops:
thousands of KM

13. Deploy by patch

14. More time spent in
automation

15. Embryonal
build/delivery
tool

16. ant - maven -
gradle - npm -
rake - etc...

17. Internet era

18. Updates are
managed by
platform

19. In the realm of
webapp the
manual deploy
reigned

20. Automated
deploy

21. Continuous
something

22. Tests

23. Virtual Machines
era

24. Distance between
devs and ops:
an office

25. Containers era

26. Serverless era

27. Monitoring
as a code

28. Distance between
devs and ops:
zero

29. Artifacts evolution
supports DevOps culture

30. Relationship
between Dev and
Ops

31. Cross-functional
teams over
organizational
silos

32. Automation
over
documentation

33. Reproducible,
scalable
and
under control

34. Funny

35. Lazy

36. GRAZIE!!
A voi
A XPeppers

37. Marco Fracassi
XP developer and trainer @ XPeppers
You can find me:
▪ Twitter: @fracassi_marco
▪ LinkedIn: https://linkedin.com/in/marco-fracassi/