The document discusses immutable infrastructure as a crucial architectural pattern within microservices architecture, highlighting its advantages over traditional models, such as avoiding configuration drift and enhancing reproducibility. It presents various tools and processes for implementing immutable infrastructure, including examples from AWS and Google Cloud, and emphasizes the significance of automation in deploying applications. Additionally, it addresses challenges in configuration management and suggests leveraging available resources and orchestration tools to build scalable and efficient systems.

1. Immutable Infrastructure
As a default architectural pattern in MSA world
JEEConf 2017
Volodymyr Tsap

2. About me
15 years supporting Linux for money
10 years Enterprise Java Applications
and SDK’s support
8 years as a CTO in own company

3. What is Immutable Infrastructure?

4. Splitting data storage with the
application environment

5. Component replacement instead
of applying configuration
changes

6. Classic Model
OS v1.0
App v1.0
Immutable model
The difference in upgrade process
App v1.1
App v1.0
OS v1.0
Reboot
Instance A
Instance A
App v1.0
OS v1.0
Instance A
App v1.1
OS v1.0
Destroy
Instance B
Start new

7. So, what the problem with Classic
Model?

8. Classic model
problems
Configuration drift

9. Classic model
problems
Configuration drift
Undocumented changes

10. Classic model
problems
Configuration drift
Undocumented changes
Weak reproducibility

11. Classic model
problems
Configuration drift
Undocumented changes
Weak reproducibility
Dev/Prod env difference

12. Classic model
problems
Configuration drift
Undocumented changes
Weak reproducibility
Dev/Prod env difference
Avoidance of automation

13. What is the Solution?
Not Exactly
?

14. Immutable Infrastructure pattern
in SHALB

15. Background Infrastructure Support,
DevOps services
40+ production environments,
including HighLoad websites,
Private Clouds, IoT vendors
and PaaS providers
30+ Development Teams, with
different stacks, OS’es,
delivery processes etc..

16. Background
Objectives:
Consolidate and unify DevOps
processes
Support more environments with
less engineers

17. Previous
Experience
Configuration Management
is not a panacea
Slow and complex development
for simple things
Software always fails somewhere

18. Decompose all supported systems
to the bricks
atomic replaceable unit

19. What could be the atomic replaceable unit?
Application instance: Elastic Beanstalk, Google App Engine
Container: Docker, RKT, LSX, Kubernetes POD
VM Image: VMDK, AMI, GCOW, ISO
Whole Infrastructure: AWS CloudFormation, Hashicorp Terraform

20. Where do we deploy units?

21. So let’s build
the units!

22. SHALB Delivery Process: Image Delivery Pipeline
OS Version
Local OS
Mirror
Build
Scenario
Packer Script
Configuration,
Software
Ansible CM
Build System
Terraform
Provision
Orchestration
Vagrant
CI/CD Auto Tests
QA Team
GIT
Infrastructure
Delivery Teams
Images
ISO, AMI,
GCOW,LXC,
Docker
Production
Development

23. SHALB Delivery Process: Custom Vanila OS Pipeline
Let's make own distro!

24. SHALB Delivery Process: Customer Related Images
Then Build Production Image

25. SHALB Delivery Process: Add software /Apply Configuration Changes
Can’t be immutable now? Use Hybrid Pipeline:

26. Summary
We can rely on any orchestration available
on premise or on public cloud.
We can scale a billions instances without the
pain managing every OS.

27. Don’t have time to build custom
pipelines?
Use available free instruments!

28. Immutable patterns
in Public Clouds
Quick Examples

29. Toolsets to build II by vendors
Docker toolset: Composer, Registry, Swarm
Amazon AWS Services, AMI-backed, AWS Container Engine
Google Cloud Immutable Images for GCE and K8
Openstack Heat Orchestration Templates
Vmware Photon Platform

30. Example #1:
AWS Elastic Beanstalk.
Immutable Deployment Method

31. AWS Elastic Beanstalk. What is this?
● Fast and simple application deployment
● Pre-installed environments Java Tomcat and Java SE
● Compile and build during deploy: javac maven ant gradle
● Auto-scaling, Load Balancing, AWS resources RDS, S3 etc..
Code Sample

32. AWS Elastic Beanstalk Deployment Options

33. Example #2: Google Cloud
Automated Image Builds with
Jenkins, Packer, and Kubernetes

34. Google Compute Engine: Raw OS image provisioned with CM

35. Google Compute Engine: Foundation image

36. Google Compute Engine: Immutable image

37. Google Guide: Automated Image Builds with Jenkins, Packer, and Kubernetes
Guide: https://cloud.google.com/solutions/automated-build-images-with-jenkins-kubernetes
Google Project on Github: https://github.com/GoogleCloudPlatform/kube-jenkins-imager

38. Example #3:
AWS CloudFormation
Infrastructure From Templates

39. Amazon CloudFormation
● Create templates for the service or application
architectures
● Quick and reliable provisioning of the services or
applications (called “stacks”).
● Update or replicate the stacks as needed.
● Sample solution templates show how to create an
end-to-end solution with common applications.

40. Amazon CloudFormation UI and Code Sample

41. To Take Away
Split your apps and the data
Deliver apps with the OS
CM approach is not a panacea
Pre-build images are more reliable and then provisioned
It is not so complex to build own image delivery

42. What to read next?

43. Using Docker. Developing and Deploying Software with Containers
http://shop.oreilly.com/product/0636920035671.do#

44. Book for SRE in Google
https://landing.google.com/sre/book/index.html

45. Terraform: Up & Running By Yevgeniy Brikman
http://www.terraformupandrunning.com/

46. Amazon Professional Services Implementation Sample
AWS re:Invent 2016: Life Without SSH: Immutable Infrastructure in Production*
https://www.slideshare.net/AmazonWebServices/aws-reinvent-2016-life-without-ssh-immutable-
infrastructure-in-production-sac318

47. Thank you! Questions?
Volodymyr Tsap
Co-founder/CTO at SHALB.com
Email: voa@shalb.com
Skype: volodymyr.tsap
Linkedin: voatsap
Facebook: volodymyr.tsap

48. Deleted slides here

49. Infrastructure as a code, versioning
Environment “time machine”, Scaling OOB
No dependencies for 3rd party repositories
Immutable Infrastructure advantages
Good for:
DevOps
Developers

50. Good for:
Quality Assurance
CI/CD integration
Quick tests for infrastructure
Immutable Infrastructure advantages

51. Perfectly fits for Microservices
Immutable Infrastructure advantages
Good for:
Software Architect
Product Managers
Product Owners

52. Maintenance cost for big deployments
Immutable Infrastructure advantages
Good for:
Business Guys
Steakholders
Product Owners