You've probably heard about "Infrastructure as Code" or "CI/CD"? Johan Siebens (@nosceon) shares his insights in how everything is increasingly turning in to code. Interested in the thoughts behind buzzwords such as Configuration Management, Infrastructure as Code, Application Environment, Continuous Integration / Delivery, Project As Code, Operations, Security & Policy Management, ... ? Then this talk is for you. With helpful tools at hand, this talk will keep you up to date in the "everything as code" world of 2020.

1. EVERYTHING
AS CODE

2. RESOURCES
■ Everything as Code: The future of ops tools, by Seth Vargo
https://www.hashicorp.com/resources/everything-as-code-the-future-of-ops-tools
■ What is Everything-as-Code? Examining the Explosion of "as Code" Buzzwords, by Mitch Pronschinske
https://hackernoon.com/everything-as-code-explained-0ibg32a3
■ Everything as Code With Terraform, by Rosemary Wang
https://www.hashicorp.com/resources/everything-as-code-with-terraform
CREDITS

3. EVERYTHING
AS CODE

4. SOME BACKGROUND
MAINFRAME SERVERS VIRTUALISATION & CLOUD

5. WE LIVE IN A WORLD THAT DEMANDS
TOOLING TO MANAGE COMPLEXITY

6. MANAGING COMPLEXITY WITH CODE
“CODIFY”
● capture a process, routine or algorithm in a textual format
● basically "write something as text"
● declarative or imperative

7. Configuration Management
01
server complexity

8. Configuration Management

9. Infrastructure As Code
02
infrastructure complexity

10. Infrastructure as Code

11. Application Environment
03
development - requirements - dependencies

12. Application Environment

13. Continuous Integration / Delivery
04
build automation

14. Continuous Integration / Delivery

15. Project As Code
05
blueprints - boilerplate - scaffolding

16. Project as Code - Scaffolding

17. Operations
06
orchestration

18. Operations

19. Security & Policy Management
07

20. Security & Policy Management

21. Everything as Code
08

22. EVERYTHING AS CODE
Blog as Code Todo as Code Pizza as Code
Test Automation RPA

23. Why?
09

24. 1. Linting, static analysis, and alerting to enforce code consistency in a large organization
2. Testing to make sure the automation works solidly
3. Collaboration: a common language to allow anyone with knowledge of the automation language to
collaborate on how it’s built
4. Separation of concerns to make it easy to give pre-packaged, best-practice modules of automation to
other groups who shouldn’t need to be experts to use the automation
5. Model abstract concepts: a model to give you an overarching conceptual map of the section of pipeline
that you’re automating.
ADVANTAGES & BENEFITS

25. What’s next?
10

26. What’s next
Less operator
interventions
AI & Machine Learning
in operations
Automatic security
scanning and patching
Serverless / Functions

27. CREDITS: This presentation template was created by Slidesgo, including
icons by Flaticon, and infographics & images by Freepik.
Please keep this slide for attribution.
Does anyone have any questions?
THANKS