The document provides 5 suggestions for building a technical infrastructure that supports constant change and innovation: 1. Use cloud-based services to avoid managing infrastructure. 2. Build systems using small, independent microservices that are easy to replace. 3. Let code repositories drive infrastructure deployment through continuous integration and delivery practices. 4. Implement an immutable infrastructure where components are replaced during each new deployment from tested, pre-built images. 5. Unify logging, monitoring, and alerting across systems for visibility and to enable automation.

1. Build a Technical
Infrastructure that
Supports Innovation
Florian Motlik
@flomotlik
flo@codeship.com

2. Pressure to Change

3. We need to deal with
constant change

4. Bad Infrastructure can
make us fail

5. 5 suggestions

6. 1. Use Services (I’m biased)

7. Infrastructure is hard

8. flomotlik.me/tools-i-like

9. 2. Build to replace

10. Small or Micro Services

11. No Infrastructure

12. Don’t be too frugal

13. Keeping workflows
consistent

14. Only focus on your code

15. 3. Let Repositories drive
Infrastructure

16. Github Flow
https://guides.github.com/introduction/flow/index.html

17. Everything deployed like
that (including DNS)

18. Great for Onboarding

19. Trivial to switch between
codebases

20. Eventually consistent
Infrastructure

21. ?
How do I build the Infrastructure

22. 4. Build an Immutable Infrastructure

23. Immutable components

24. Replace for every
deployment

25. New Image per deployment

26. Fully tested and validated

27. Deployment
New Release Test Build and
Verify
Image Store
897gsd9fg
5123hkhk
ydo4m2jd8
74kdf7oefhf

28. Create Image
New Release Test Build and
Verify
Image Store
90jh0hjfdh
897gsd9fg
5123hkhk
ydo4m2jd8
74kdf7oefhf

29. Current System
Loadbalancers
Application Cluster
897gsd9fg
Database

30. Deployment
Loadbalancers
Application Cluster
897gsd9fg
Database
Application Cluster
90jh0hjfdh

31. Switch
Loadbalancers
Application Cluster
897gsd9fg
Application Cluster
90jh0hjfdh
Database

32. Destroy when no errors
Loadbalancers
Application Cluster
897gsd9fg
Application Cluster
90jh0hjfdh
Database

33. New System
Loadbalancers
Application Cluster
90jh0hjfdh
Database

34. Siloed State
Loadbalancers
90jh0hjfdh Stateless
State Silo
Application Cluster
Database
Application Cluster
897gsd9fg

35. Deploy = Rollback

36. ?
Any problems with small services
that are often deployed

37. Operations and Overview

38. 5. Unify Logging, Monitoring and
Alerting

39. One source of truth

40. Logs are very underused

41. Make Data Accessible

42. Chat Ops

43. Skipping here costs 100x

44. Automate scaling and
healing with metrics

45. 1. Use Services
2.Build to replace
3.Let Repositories drive Infrastructure
4.Build an immutable Infrastructure
5.Unify Logging, Monitoring and Alerting

46. Focus on your
Code and Product

47. QA (or send me an email)
flo@codeship.com

48. Thank you
flomotlik.me/tools-i-like
@flomotlik
flo@codeship.com