Some basic concepts of Infrastructure As Code. With some practical Terraform demo and examples.

1. Infrastructure as Code
Joe Tavin

2. ● Why is IAC important?
● IAC Principles and Paradigms
● Terraform, popular IAC tool
2

3. 3

4. 4

5. About Me
● BSc. Computer Science
● Site Reliability Engineer at BigPanda.
● 10 years in the industry, Cloud/DevOps/Platform/SRE
roles at Exlibris, Moovit and more.
5

6. “Site Reliability Engineering is what you
get when you treat Operations like a
Software Problem and you staff it with
Software Engineers”
Benjamin Treynor Sloss, VP 24X7
SRE Founder @ Google
6

7. Business Dictates Software Development
● Lean and Agile have taken over Modern SAAS, from
Enterprise to Consumer software.
● Software Development adopted Microservices.
7

8. Monolith
Application = {ONE BIG APPLICATION, Many Features }
8

9. My Monolithic Application - 2012
● Application Software
● Databases - Oracle, MySQL
● 3rd Parties - OpenSSL, Apache, Tomcat
9

10. Microservices
Application = { Microservice 1 = Feature 1,
Microservice 2 = Feature 2,
Microservice 3 = Feature 3 }
10

11. My Microservices Architecture - 2022
● Server Clusters
● Containers Runtime and Orchestration, (Docker, Kubernetes)
● Serverless Functions
● Networking, Load Balancers
● Datastores - RDBMS, NoSQL, Caches, Object Storage
● 3rd Party Tools and Libraries
● PubSub Systems (Apache Kafka, RabbitMQ)
● Cloud Services
● Fully Managed Services, (Snowflake, MongoDB Atlas, Elastic Cloud)
11

12. What do want our
Infrastructure to be?
12

13. Facebook Developer Slogan
“Move fast, break things”
13

14. Changed to
“Move fast, with stable
Infrastructure” in 2014
14

15. Infrastructure should be Agile
But Dependable
15

16. Fast Moving Infrastructure Requirements
● Reduced Manual Labor
● Fast Deployments
● Environments Consistency
● Configure Once, Run Anywhere
16

17. Software Development
Principles
17

18. Object Oriented Programming
● Encapsulation
● Abstraction
● Inheritance
● Polymorphism
18

19. IAC = Agile Operations +
Software Engineering
Principles => Business Impact
19

20. Business Impact
● Fast Deployments => Lean, Agile
● Reduced Manual Labor => Lean, Agile
Software Engineering Principles
● Environments Consistency => Encapsulation,
Polymorphism
● Configure Once, Run Anywhere => Abstraction,
Inheritance
20

21. 21

22. Codifying Infrastructure.
What?
22

23. Microservices and Providers
● Number of Microservices
● Many Infrastructure Providers
23

24. Providers
● More Services need Infrastructure
● More Infrastructure “Providers” for each service:
○ Servers
○ Storage
○ Databases
○ Queues
○ Caches
○ etc..
24

25. Codifying Infrastructure.
How?
25

26. Services define programmable
specs for each of their
infrastructure Providers.
26

27. The Imperative Approach
27

28. NxM Problem
● N Microservices
● M Infrastructure Providers
28
Source

29. Declarative Approach
29

30. 30

31. N+M Solution
● Intent Model = Declarative Approach
● Abstract Infrastructure Providers
● Tool Enforces Infrastructure State
31

32. IAC Demo
– Terraform –
32

33. Terraform
● Hashicorp - 2014
● Open Source
● Written in Go
● Provider Architecture
● Declarative Syntax!
33

34. Terraform Providers
● AWS
● Azure
● Google Cloud
● Datadog
● Databricks
● Many many more
● Write your own!
34

35. Usage
● Initialization => Installs Providers
35

36. State
● Local State File
● State can be Remote (This is best practice as well)
36

37. Demo!
● Create EC2 Server using Terraform
37

38. Questions?
38

39. Thank You!
39
https://www.linkedin.com/in/jtavin/ 📧 jtavin@gmail.com 📱 054-595-3376