This document discusses the evolution of developer jobs and the end of server management. It argues that developers are creating industrialized tools and frameworks to automate software production. The cloud has introduced infrastructure as a service (IAAS), but there is still manual work required. True hosting platforms should allow software to deploy without downtime and handle scaling automatically like a commodity like electricity. Developers should focus on coding while platform managers maintain the hosting environment. This represents the end of manual server management, similar to how people no longer manage individual power plants.

1. THE END OF
SERVER
MANAGEMENT &
THE EVOLUTION OF
DEVELOPER JOB
QUENTIN ADAM
@WAXZCE

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

3. MY DAY TO DAY WORK :
CLEVER CLOUD, MAKE YOUR
APP RUN ALL THE TIME

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. WHAT’S NEXT IN 20 YEARS?

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. THE COMPUTER

25. VERY EFFICIENT TOOL TO
INDUSTRIALIZE BRAIN POWER

26. THE ENGINE FOR INTELLECTUAL
SERVICES COMMODITIZATION

27. WE ARE IN THE ERA OF INDUSTRIAL
REVOLUTION

28. EXAMPLES

29. COMPARING PRICES

30. MATH

31. ACCOUNTABILITY

32. TRANSLATION ? IMAGE RECOGNITION ?

33. MACHINE LEARNING WITH NEURAL
NETWORK

34. SO,

35. DEVELOPERS DEVELOPERS DEVELOPERS

36. WE CREATE
TOOLS

37. WE CREATING POWER TOOLS TO
INDUSTRIALIZE BRAIN POWER

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

39. TOOLS TO IMPROVE BUSINESS

40. TOOLS TO IMPROVE LIFE

41. TOOLS TO IMPROVE THE WORLD

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

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

44. THIS IS WHY STARTUPS ARE
DISRUPTING MARKETS

45. *Not Invented Here
SOFTWARE IS EATING THE WORLD

46. THEN DEVELOPERS BECOME MORE
AND MORE IMPORTANT TO BUSINESSES

47. DEVELOPERS RULE BUSINESS

48. SOFTWARE WAS AN INVESTMENT

49. DO YOU HEARD ABOUT V PROCESS?

50. WE WERE CREATING ASSETS LIKE REAL
ESTATE

51. BUT NOW SOFTWARE IS A
CONTINUOUS DELIVERY SERVICE

52. CONSTANT IMPROVEMENT

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

54. BECAUSE WE CAN IMPROVE
CONTINUALLY OUR INDUSTRIAL ASSET

55. WE ACTING ON DATA

56. MANAGE DATA PROCESS AND DATA
MANAGEMENT

57. CREATING A DATA PIPE

58. Akka-stream RxStream example
REACTIVE ?

59. BUT WE BECOME ARCHITECTS OF THE
BUSINESS FACTORY

60. WE ARE NOT BLUE COLLAR WORKERS
ANYMORE

61. WE NEED TO CONNECT TO THE VISION
OF BUSINESS

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

63. IT’S A SKILL FOR BUSINESS
ARCHITECTS

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

65. SO,

66. WE CREATE SOFTWARE

67. FRAMEWORKS

68. BUILD TOOLS

69. SOURCE MANAGEMENT

70. CONTINUOUS INTEGRATION….

71. FULLY AUTOMATED SOFTWARE
FACTORY

72. INDUSTRIAL

73. AND WE DEPLOY IT ON SERVERS

74. A SERVER

75. WITH AN OPERATING SYSTEM

76. RUNNING MIDDLEWARE AND
SOFTWARE

77. MONITORING

78. BACKUPS

79. IS IT AN INDUSTRIAL WAY TO THINK?

80. CLOUD IS
HERE,
THERE IS
IAAS

81. YOU CAN USE A VIRTUAL SERVER

82. BUT STILL THERE ARE SOME MANUAL
TASKS TO PERFORM

83. IS THIS PLUGGABLE?

84. LIKE ELECTRICITY

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

86. OWN ELECTRICITY PRODUCTION

87. PRODUCTION LINE IS POISONED BY
ELECTRICITY PRODUCTION

88. DEEP DEPENDENCY LINKING

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

90. DO YOU HAVE AN ELECTRICITY
PROJECT?

91. BUT TODAY YOU HAVE HOSTING
PROJECTS

92. BECAUSE THERE IS NO INDUSTRIAL
WAY TO DO IT

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

94. WAKE UP!

95. PRODUCTION HAS TO BE PERFECT

96. PEOPLE ARE NOT PERFECT

97. PEOPLE HAVE NOTHING TO DO ON
PRODUCTION STUFF

98. ULTRON

99. AT CLEVER CLOUD SSH CONNECTION
IS A RED ALERT

100. WE NEED TO BUILD A HOSTING
PLATFORM

101. STANDARD WAY TO HOST SOFTWARE
WITHOUT THINKING ABOUT IT

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

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

104. HARDWARE
+
SOFTWARE
+
SERVICE

105. WORK OF DEVELOPER HAS TO STOP AT
GIT PUSH

106. APPLICATIONS HAVE TO DEPLOY

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

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

109. USE BUILD SYSTEMS

110. 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

111. UPDOWNSCALING HAS TO BE HANDLED
BY THE PLATFORM ITSELF

112. OUTSCALING HAS TO BE HANDLED BY
THE PLATFORM ITSELF

113. RELAUNCH ON FAILURE

114. BACKUP POLICY

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

116. IT’S A FULL-TIME JOB

117. MAINTAINED BY PLATFORM MANAGERS

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

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

120. JUST LIKE ELECTRICITY

121. THIS IS THE END OF SERVER
MANAGEMENT

122. RESPECTING COMMODITY STANDARDS

123. ARE YOU CALLING PEOPLE FROM THE
POWER PLANT WHEN YOU’RE
INSTALLING A NEW TV?

124. WE NEED TO WORK LIKE AN INDUSTRY

125. I.E. BUILDING A SCALABLE
PRODUCTION LINE FOR INTELLECTUAL
SERVICES

126. CODE & INFRASTRUCTURE
ARCHITECTURE INSIGHT

127. ONE VIRTUAL MACHINE = ONE TASK

128. CLUSTER AND SCALE OUT
MODEL NOT ONLY FOR HUGE
LOAD

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

130. NO MORE OLYMPIC CONTEST ON
UPTIME

131. Clusterable
application
Immutable
architecture
Template
based
deployment
No
maintenance
Decrease the
tooling on the
server
Able to
rebuild all
infrastructure
NEVER
BUILD
LEGACY
SYSTEM

132. IMMUTABILITY

133. DO NOT USE THE FILE SYSTEM AS A
DATASTORE

134. DO NOT USE THE FILE
SYSTEM AS A DATASTORE
File system are POSIX compliant
• POSIX is ACID
• POSIX is powerful but is a bottleneck
• File System is the nightmare of ops
• File System creates coupling (host provider/OS/language)
• SPOF-free multi tenant File System is a unicorn
STORE IN DATABASE, OR IN A DATASTORE LIKE
S3/RIAKCS DEDICATED TO FILE MANAGEMENT

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

136. SMALLEST CODE BASE POSSIBLE
FOR EACH PROGRAM

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

138. BE CONSISTENT AND PREDICTABLE

139. FOCUS ON THE BEST TOOL
TO SOLVE YOUR PROBLEM

140. SCALE YOUR TEAM
MODULARIZE YOUR TEAM

141. THE POWER OF
REWRITE EVERYTHING

142. SMALL CODE BASE + MULTIPLE
TECHNOLOGIES =
LEGACY KILLER

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

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

145. CONSIDER MORE
THINGS AS DATA
• User account
• Users data
• Files
• Sessions
• Events

146. DATA QUALIFICATION

147. TRUST YOUR
MIDDLEWARE

148. USE AN EVENT BROKER TO
MODULARIZE YOUR APP

149. TRACK BUG & GET METRICS

150. CAREFUL USE OF DARK MAGIC

151. DON’T BE THAT GUY

152. DO NOT USE A
TECHNOLOGY BECAUSE
YOU <3 IT OR BECAUSE
IT’S HYPE : USE IT
BECAUSE IT FITS YOUR
NEEDS
BALANCE YOUR LEARNING CURVE WITH
THE TIME SAVED

153. DO NOT CREATE MONSTERS

154. GIVE A TRY TO TECHNOLOGY

155. FOCUS ON YOUR ADDED VALUE

156. DEVELOPERS ARE EVERYWHERE

157. IT’S A WAR OUT THERE

158. WE NEED DEVELOPERS TO RULE THE
FORTUNE 500 COMPANIES ;-)

159. Give CLEVER-CLOUD.COM a try with this coupon : devoxxplroxx15
I’m @waxzce on twitter
THX FOR LISTENING