This document discusses the evolution of server management and the rise of platforms that allow developers to focus on building applications rather than managing infrastructure. It argues that server management should be fully automated and handled by dedicated platform managers, freeing up developers to focus on code, architecture, and business value. The document also advocates for a modular approach to application development using microservices and immutable infrastructure managed by platforms as a commodity service.

1. THE END OF
SERVER
MANAGEMENT
QUENTIN ADAM
@WAXZCE
CLEVER CLOUD

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. And learn a lot of things about your code, apps, and good/bad design…
KEEP YOUR APPS ONLINE. MADE WITH
NODE.JS, SCALA, JAVA, RUBY, PHP,
PYTHON, GO…

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

6. OUR INDUSTRY IS A GAME CHANGER
BUT IT’S STILL VERY YOUNG

7. IT’S ABOUT 30/40 YEARS OLD

8. FROM NOTHING TO BILLION $
COMPANIES AND IMPRESSIVE MARKET

9. AND WHAT ABOUT HOW WE WORK?

10. TAKE SOME TIME TO THINK ABOUT

11. MANKIND IS EVOLVING

12. Ray Kurzweil – “The Law of Accelerating Returns”
AND PROGRESS MAKES THE NEXT
TECHNOLOGICAL STEP CLOSER

13. WE HAVE BUILT OUR WORLD TO
ENHANCE OUR LIVES

14. AND TO BE ABLE TO MANAGE THE
POPULATION GROWTH

15. THIS IS WHY WE CREATE TOOLS

16. TO ENHANCE PRODUCTION

17. ACHIEVING TO INDUSTRIALIZE THE
PRODUCTION

18. WHAT IS
INDUSTRY?

19. A COST EFFICIENT WAY TO PRODUCE
LARGE VOLUME

20. A REPEATABLE AND SCALABLE
PROCESS

21. ACHIEVING TO CREATE “COMMODITY”
RESPONSE TO A NEED

22. THE 19TH WAS THE CENTURIES WHEN
WE INDUSTRIALIZE MANUFACTURING

23. ALLOWED BY THE ENGINE

24. TODAY

25. THE COMPUTER

26. VERY EFFICIENT TOOL TO
INDUSTRIALIZE BRAIN POWER

27. THE ENGINE FOR INTELLECTUAL
SERVICES COMMODITIZATION

28. WE ARE IN THE ERA OF INDUSTRIAL
REVOLUTION

29. EXAMPLES

30. COMPARING PRICES

31. MATH

32. ACCOUNTABILITY

33. TRANSLATION ? IMAGE RECOGNITION ?

34. MACHINE LEARNING WITH NEURAL
NETWORK

35. SO,

36. DEVELOPERS DEVELOPERS DEVELOPERS

37. WE CREATE
TOOLS

38. WE CREATING POWER TOOLS TO
INDUSTRIALIZE BRAIN POWER

39. I.E.
ECONOMY IS MANAGING THE HUMAN
PRODUCTIVITY

40. TOOLS TO IMPROVE BUSINESS

41. TOOLS TO IMPROVE LIFE

42. TOOLS TO IMPROVE THE WORLD

43. BECAUSE WE KNOW AND UNDERSTAND
THE PROCESS TO CREATE VALUE

44. BECAUSE WE KNOW AND UNDERSTAND
THE PROCESS TO CREATE MONEY

45. THIS IS WHY STARTUPS ARE
DISRUPTING MARKETS

46. *Not Invented Here
SOFTWARE IS EATING THE WORLD

47. THEN DEVELOPERS BECOME MORE
AND MORE IMPORTANT TO BUSINESSES

48. DEVELOPERS RULE BUSINESS

49. SOFTWARE WAS AN INVESTMENT

50. DO YOU HEARD ABOUT V PROCESS?

51. WE WERE CREATING ASSETS LIKE REAL
ESTATE

52. BUT NOW SOFTWARE IS A
CONTINUOUS DELIVERY SERVICE

53. CONSTANT IMPROVEMENT

54. SOME CREATE PROCESSES, OTHERS
CREATE LOW LEVELS THINGS TO BUILD
PROCESSES ON

55. BECAUSE WE CAN IMPROVE
CONTINUALLY OUR INDUSTRIAL ASSET

56. BUT WE BECOME ARCHITECTS OF THE
BUSINESS FACTORY

57. WE ARE NOT BLUE COLLAR WORKERS
ANYMORE

58. WE NEED TO CONNECT TO THE VISION
OF BUSINESS

59. DEVELOPING IS NO LONGER A JOB. IT’S
A POINT OF VIEW

60. IT’S A SKILL FOR BUSINESS
ARCHITECTS

61. BUILDER OF BRAIN INDUSTRY TOOLS
TO ACHIEVE PROGRESS NEXT STEP

62. SO,

63. WE CREATE SOFTWARE

64. FRAMEWORKS

65. BUILD TOOLS

66. SOURCE MANAGEMENT

67. CONTINUOUS INTEGRATION….

68. FULLY AUTOMATED SOFTWARE
FACTORY

69. INDUSTRIAL

70. AND WE DEPLOY IT ON SERVERS

71. A SERVER

72. WITH AN OPERATING SYSTEM

73. RUNNING MIDDLEWARE AND
SOFTWARE

74. MONITORING

75. BACKUPS

76. IS IT AN INDUSTRIAL WAY TO THINK?

77. CLOUD IS
HERE,
THERE IS
IAAS

78. YOU CAN USE A VIRTUAL SERVER

79. BUT STILL THERE ARE SOME MANUAL
TASKS TO PERFORM

80. IS THIS PLUGGABLE?

81. LIKE ELECTRICITY

82. THINK ABOUT ELECTRICITY AT THE
BEGINNING OF 20TH CENTURY

83. OWN ELECTRICITY PRODUCTION

84. PRODUCTION LINE IS POISONED BY
ELECTRICITY PRODUCTION

85. DEEP DEPENDENCY LINKING

86. BUY ELECTRICITY, NOT A POWER
PLANT. IT’S A COMMODITY

87. DO YOU HAVE AN ELECTRICITY
PROJECT?

88. BUT TODAY YOU HAVE HOSTING
PROJECTS

89. BECAUSE THERE IS NO INDUSTRIAL
WAY TO DO IT

90. BECAUSE OPS TODAY IS A (SOMEWHAT
FINE) TAILORED THING MADE BY
PEOPLE

91. WAKE UP!

92. PRODUCTION HAS TO BE PERFECT

93. PEOPLE ARE NOT PERFECT

94. PEOPLE HAVE NOTHING TO DO ON
PRODUCTION STUFF

95. ULTRON

96. AT CLEVER CLOUD SSH CONNECTION
IS A RED ALERT

97. WE NEED TO BUILD A HOSTING
PLATFORM

98. STANDARD WAY TO HOST SOFTWARE
WITHOUT THINKING ABOUT IT

99. THERE IS NO PLACE FOR OPS, JUST
PLATFORM MANAGERS

100. THE SO CALLED PLATFORM: BUT WHAT
IS A PLATFORM?

101. HARDWARE
+
SOFTWARE
+
SERVICE

102. WORK OF DEVELOPER HAS TO STOP AT
GIT PUSH

103. APPLICATIONS HAVE TO DEPLOY

104. (WITHOUT DOWNTIME)
BECAUSE YOU NEED TO BE ABLE TO
PUT NEW VERSIONS IN PRODUCTION
EASILY

105. It’s nonsense to be unable to do continuous deployment
AVOID THE MAINTENANCE TIME

106. USE BUILD SYSTEMS

107. Carefully : who is on charge of updates? Containers are not isolated as VM, can you
share your kernel?
OR DOCKER AS AN OPERATING SYSTEM
BUILDER

108. UPDOWNSCALING HAS TO BE HANDLED
BY THE PLATFORM ITSELF

109. OUTSCALING HAS TO BE HANDLED BY
THE PLATFORM ITSELF

110. RELAUNCH ON FAILURE

111. BACKUP POLICY

112. SECURITY
Developers
• Code dependencies
• Application process
Platform manager
• OS
• Hypervision
• Infrastructure
• Platform

113. PRODUCTION BINARY ?

114. IT’S A FULL-TIME JOB

115. MAINTAINED BY PLATFORM MANAGERS

116. Instead of 200 to 500
FACEBOOK EXAMPLE:
ONE TECHNICIAN IN THE DATA CENTER
FOR EVERY 25,000 SERVERS

117. AND NOT A THING TO DO OR THINK
ABOUT FOR DEVELOPERS

118. JUST LIKE ELECTRICITY

119. THIS IS THE END OF SERVER
MANAGEMENT

120. LAYERS: WHAT IS MY ADDED VALUE?

121. AUTOMATE ALL THE NON VALUED
PARTS

122. OR BRING THIS ON TOP OF A PUBLIC
CLOUD MANAGING IT

123. PUSH TO
COMMODITY

124. FOCUS ON BUILDING

125. CODE & INFRASTRUCTURE
ARCHITECTURE INSIGHT

126. NO MORE OLYMPIC CONTEST ON
UPTIME

127. IMMUTABILITY

128. DO NOT USE THE FILE SYSTEM AS A
DATASTORE

129. SPLIT THE CODE :
MODULES
• Smallest code
base
• Deploy as
service for
each other
• Focus on best
technology for
a problem

130. SMALLEST CODE BASE POSSIBLE
FOR EACH PROGRAM

131. SCALE YOUR TEAM
MODULARIZE YOUR TEAM

132. SMALL CODE BASE + MULTIPLE
TECHNOLOGIES =
LEGACY KILLER

133. THE POWER OF
REWRITE EVERYTHING

134. REWRITE IS QUICK BECAUSE
YOU KNOW ALL THE PROBLEMS
BEFORE IT HAPPENS

135. EACH MODULE
IS VIEWED AS
A SERVICE BY
OTHERS
HTTP OR AMQP COMUNICATION
OR AS A CLIENT

136. BE CONSISTENT AND PREDICTABLE

137. CAREFUL USE OF DARK MAGIC

138. FOCUS ON YOUR ADDED VALUE

139. CLEVER
CLOUD
5 YEARS OLD EXPERIMENT

140. ARCHITECTURE
OVERVIEW

141. INCREMENTAL
ARCHITECTURE
1. Configuration file generator
2. Quick fix
3. More resource to buy time
4. Real full-featured solution
5. Kill legacy

142. Give CLEVER-CLOUD.COM a try 
I’m @waxzce on twitter
THX FOR LISTENING