Why everybody is speaking about Immutability? Immutable infrastructure? The All IT automation ecosystem need to rely on the append only, remove historical management of servers. This talk explain what is immutable infrastructure, how to build it, and how to manage data in this infrastructure pattern. It will cover pattern to use it on containers or virtual machine world.

1. IMMUTABLE
INFRASTRUCTURE,
WHY, WHEN & HOW
@WAXZCE
QUENTIN ADAM AT

2. Quentin ADAM from the Clever Cloud
@waxzce on twitter – github- soundcloud – instagram ….
WHO AM I ?

3. MY DAY TO DAY WORK :
CLEVER CLOUD,
THE IT AUTOMATION COMPANY

4. KEEP YOUR APPS ONLINE. MADE WITH
NODE.JS, SCALA, JAVA, RUBY, PHP,
PYTHON, GO…
Cloud & on premise ;-)

5. AND LEARN A LOT OF THINGS ABOUT
YOUR CODE, APPS, AND GOOD/BAD
DESIGN…

6. GIVE BACK TO THE COMMUNITY
NEVER
GONNA
LET YOU
DOWN
clever-cloud.com

7. LET’S TALK ABOUT
INFRASTRUCTURE

8. 40 times in 5 years price drop of AWS
SERVERS COSTS ARE GOING DOWN

9. Google I/O 2015
“RACE TO ZERO”
I.E THE SERVER IS FREE

10. In fact, all you have is…
COOL.
YOU HAVE A SERVER.

11. HOSTING
Backup Updates Certification
Agreement Process Provisioning
Security
Hardware
maintenance

12. VALUE
= SERVER
MANAGEMENT

13. ONCE UPON A TIME, MY BELOVED
SERVERS

14. THEN, VIRTUALIZED ONES

15. CREATE HISTORY

16. DOCUMENTATION

17. SPECIFIC

18. TAYLOR MADE

19. NOT ABLE TO SCALE

20. KNOWLEDGE
!=
AUTOMATION

21. Automate
SPLIT COMPLEX PROBLEMS INTO A
COLLECTION OF SMALL ONES

22. POSSIBLE SERVERS
STATES
…
Updated to
V43
New
configuration
files
Install new
service
History …

23. AVOID HISTORY

24. FIX STATE OF
THE DATA TO
ENSURE
ACCESSIBILITY

25. POSSIBLE STATE IN
AN IMMUTABLE STATE
working
Not
working
Very simple to predicate

26. FIX THE
HISTORY IN A
IMMUTABLE
STATE

27. BTW,
REAL WORLD
INSIGHT
“WE LIVE IN A MUTABLE WORLD, DEAL WITH IT”

28. WORLD IS
SUCCESSION
OF
IMMUTABLE
INSTANT

29. EPHEMERAL
IMMUTABLE
INSTANCES

30. PET
!=
CATTLE

31. SERVICE
UPTIME
!=
SERVER
UPTIME

32. NO MORE OLYMPIC CONTEST ON
UPTIME

33. And why it’s a problem to manage technical product and decision with book keepers
point of view https://www.youtube.com/watch?v=0ip1FoBsLB4
(AWS PRICING HYPOCRISY LEAD TO
BAD PRACTICE)
Summon Yog-Sothoth

34. HUMANLESS
POWERTOOLS

35. PRODUCTION HAS TO BE PERFECT

36. PEOPLE ARE NOT PERFECT

37. PEOPLE HAVE NOTHING TO DO ON
PRODUCTION STUFF

38. AT CLEVER CLOUD SSH CONNECTION
IS A RED ALERT

39. CAPACITY PLANNING

40. SPLIT PROCESS AND
STORAGE
Storage
• Databases
• Files
• Sessions
• Events
• …
Code
• Can be replicated
• Stateless
• Process

41. RUNTIME INSTANCES

42. VM, docker, kubernetes, puppet, ansible, vmware… This is not the problem
TECHNOLOGIES?

43. THERE IS ONE PROCESS:
BUILD

44. THEN, REGISTER

45. AND LIVE WITHOUT DATA

46. AND DIE WHEN MORE
UPDATED VERSION IS THERE

47. TRASH OLD VERSION

48. FULLY AUTOMATED HOSTING FACTORY

49. AN INSTANCE IS DEAD OR ALIVE AND
THAT’S ALL

50. APP FAIL?
REDEPLOY
NEW
INSTANCE

51. OPERATION
SYSTEM
UPDATE ?
REDEPLOY
NEW
INSTANCE

52. REBALANCE
HARDWARE
ALLOCATION?
REDEPLOY
NEW
INSTANCE

53. PREDICABLE
FAIL OF THE
APPLICATION?
REDEPLOY
NEW
INSTANCE

54. Picking one instance or another doesn’t matter
STATELESSNESS IS THE KEY

55. BECAUSE YOU WILL NOT RELY
ON A SERVER ANYMORE

56. CREATE A FACTORY OF INSTANCE

57. PROXY
AND
ROUTING

58. Consul, etcd, Clever Cloud service dependencies
SERVICE DISCOVERY

59. CONFIGURATION
=> ENVIRONMENT VARIABLE

60. HOW TO MANAGE DATA?

61. SPLIT DATA AND PROCESS:
FS COMPOSITION
Runtime
• local
• replicable
• updated
Data
• file system
• block storage
• replicated
• copy on write?

62. DATA
STORAGE
WAYS

63. Not part of this list
DATABASE (ACID OR NOT, SQL OR NOT)

64. FILE SYSTEM

65. BLOC STORAGE

66. OBJECT STORAGE

67. (COPY ON WRITE)

68. (COPY ON WRITE)

69. DATA MANAGEMENT IS BIND
TO DB NEEDS

70. ACID :
DUPLICATE & DATA EVOLUTION

71. INSTANCE FOR ONE
ORGANIZATION
ACID
• Atomicity
• Consistency
• Isolation
• Durability
Powerful
data
management
• Transaction
• User
management
• One above one
Take advantage of ACID
database

72. BUT IT DESIGNS A
BOTTLENECK

73. EXAMPLE : E-SHOP ON
CLASSIC MODE

74. EXAMPLE : E-SHOP ON
CLASSIC MODE
User A buy a
hdd
Database Transaction :
• Stock management
• Order management
• Invoice generation
• Customer Account reward
• …
Transaction
user A is
processed
Stock &
Order are just
perfectly
synchronize

75. EXAMPLE : E-SHOP ON
CLASSIC MODE
User A buy a
hdd
Database Transaction :
• Stock management
• Order management
• Invoice generation
• Customer Account reward
• …
Transaction
user A is
processed
Stock &
Order are just
perfectly
synchronize
User B buy a
hdd Transaction
user B is
processed
then

76. EXAMPLE : E-SHOP ON
MULTI-TENANT MODE
i.e. : Multiple shop of various sellers on the same instance

77. EXAMPLE : E-SHOP ON
MULTI-TENANT MODE
User A buy a
hdd on seller A
Database Transaction :
• Stock management
• Order management
• Invoice generation
• Customer Account reward
• …
Transaction
user A is
processed
Stock &
Order are just
perfectly
synchronize
User B buy a
book on seller B Transaction
user B is
processed
then

78. HIGH AVAILABILITY:
DISTRIBUTED SYSTEM

79. DISTRIBUTED
DB AND
HARDWARE
DAFUCKNESS

80. FORGET THE SAN, GO FULL
DISTRIBUTED

81. BE CONSISTENT AND PREDICTABLE

82. MONITORING
IS
MANDATORY

83. IMMUTABILITY
AS A PATTERN
ANOTHER TALK FROM ME ;-)
FR version : https://www.youtube.com/watch?v=y1BR7Rh7FSY&t=15s

84. I’m on twitter : @waxzce
quentin.adam@clever-cloud.com
THANK YOU !
ANY QUESTIONS ?
Clever Cloud gift coupon:
BuildStuffUA16