This document discusses becoming a modern developer and the industrialization of software development. It advocates for treating software development like a factory process that is highly automated, standardized, and focused on continuous delivery. Specific techniques mentioned include making code modular and stateless, storing data separately from code, using immutable infrastructure, and rewriting systems from scratch to avoid technical debt. The goal is to remove as much manual work as possible and commoditize hosting so developers can focus on their primary work of building software.

1. BE A MODERN
DEVELOPER
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, 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. MANKIND IS EVOLVING

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

12. WE HAVE BUILT OUR WORLD TO
ENHANCE OUR LIVES

13. AND TO BE ABLE TO MANAGE THE
POPULATION GROWTH

14. THIS IS WHY WE CREATE TOOLS

15. TO ENHANCE PRODUCTION

16. ACHIEVING TO INDUSTRIALIZE THE
PRODUCTION

17. WHAT IS
INDUSTRY?

18. A COST EFFICIENT WAY TO PRODUCE
LARGE VOLUME

19. A REPEATABLE AND SCALABLE
PROCESS

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

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

22. ALLOWED BY THE ENGINE

23. THE COMPUTER

24. VERY EFFICIENT TOOL TO
INDUSTRIALIZE BRAIN POWER

25. THE ENGINE FOR INTELLECTUAL
SERVICES COMMODITIZATION

26. WE ARE IN THE ERA OF INDUSTRIAL
REVOLUTION

27. EXAMPLES

28. COMPARING PRICES

29. MATH

30. ACCOUNTABILITY

31. TRANSLATION ? IMAGE RECOGNITION ?

32. MACHINE LEARNING WITH NEURAL
NETWORK

33. SO,

34. DEVELOPERS DEVELOPERS DEVELOPERS

35. WE CREATE
TOOLS

36. WE CREATING POWER TOOLS TO
INDUSTRIALIZE BRAIN POWER

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

38. TOOLS TO IMPROVE BUSINESS

39. TOOLS TO IMPROVE LIFE

40. TOOLS TO IMPROVE THE WORLD

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

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

43. THIS IS WHY STARTUPS ARE
DISRUPTING MARKETS

44. *Not Invented Here
SOFTWARE IS EATING THE WORLD

45. THEN DEVELOPERS BECOME MORE
AND MORE IMPORTANT TO BUSINESSES

46. DEVELOPERS RULE BUSINESS

47. SOFTWARE WAS AN INVESTMENT

48. DO YOU HEARD ABOUT V PROCESS?

49. WE WERE CREATING ASSETS LIKE REAL
ESTATE

50. BUT NOW SOFTWARE IS A
CONTINUOUS DELIVERY SERVICE

51. CONSTANT IMPROVEMENT

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

53. BECAUSE WE CAN IMPROVE
CONTINUALLY OUR INDUSTRIAL ASSET

54. WE ACTING ON DATA

55. MANAGE DATA PROCESS AND DATA
MANAGEMENT

56. CREATING A DATA PIPE

57. BUT WE BECOME ARCHITECTS OF THE
BUSINESS FACTORY

58. WE ARE NOT BLUE COLLAR WORKERS
ANYMORE

59. WE NEED TO CONNECT TO THE VISION
OF BUSINESS

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

61. IT’S A SKILL FOR BUSINESS
ARCHITECTS

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

63. SO,

64. WE CREATE SOFTWARE

65. FRAMEWORKS

66. BUILD TOOLS

67. SOURCE MANAGEMENT

68. CONTINUOUS INTEGRATION….

69. FULLY AUTOMATED SOFTWARE
FACTORY

70. INDUSTRIAL

71. AND WE DEPLOY IT ON SERVERS

72. A SERVER

73. WITH AN OPERATING SYSTEM

74. RUNNING MIDDLEWARE AND
SOFTWARE

75. MONITORING

76. BACKUPS

77. IS IT AN INDUSTRIAL WAY TO THINK?

78. CLOUD IS
HERE,
THERE IS
IAAS

79. YOU CAN USE A VIRTUAL SERVER

80. BUT STILL THERE ARE SOME MANUAL
TASKS TO PERFORM

81. IS THIS PLUGGABLE?

82. LIKE ELECTRICITY

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

84. OWN ELECTRICITY PRODUCTION

85. PRODUCTION LINE IS POISONED BY
ELECTRICITY PRODUCTION

86. DEEP DEPENDENCY LINKING

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

88. DO YOU HAVE AN ELECTRICITY
PROJECT?

89. BUT TODAY YOU HAVE HOSTING
PROJECTS

90. BECAUSE THERE IS NO INDUSTRIAL
WAY TO DO IT

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

92. WAKE UP!

93. PRODUCTION HAS TO BE PERFECT

94. PEOPLE ARE NOT PERFECT

95. PEOPLE HAVE NOTHING TO DO ON
PRODUCTION STUFF

96. ULTRON

97. AT CLEVER CLOUD SSH CONNECTION
IS A RED ALERT

98. WE NEED TO BUILD A HOSTING
PLATFORM

99. STANDARD WAY TO HOST SOFTWARE
WITHOUT THINKING ABOUT IT

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

101. OPS <-> DEV
COMMUNICATION STANDARD

102. LAYERS: WHAT IS MY ADDED VALUE?

103. AUTOMATE ALL THE NON VALUED
PARTS

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

105. PUSH TO
COMMODITY

106. FOCUS ON BUILDING

107. CODE & INFRASTRUCTURE
ARCHITECTURE INSIGHT

108. ONE VIRTUAL MACHINE = ONE TASK

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

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

111. NO MORE OLYMPIC CONTEST ON
UPTIME

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

113. IMMUTABILITY

114. DO NOT USE THE FILE SYSTEM AS A
DATASTORE

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

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

117. SMALLEST CODE BASE POSSIBLE
FOR EACH PROGRAM

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

119. BE CONSISTENT AND PREDICTABLE

120. FOCUS ON THE BEST TOOL
TO SOLVE YOUR PROBLEM

121. SCALE YOUR TEAM
MODULARIZE YOUR TEAM

122. THE POWER OF
REWRITE EVERYTHING

123. SMALL CODE BASE + MULTIPLE
TECHNOLOGIES =
LEGACY KILLER

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

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

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

127. DATA QUALIFICATION

128. TRUST YOUR
MIDDLEWARE

129. USE AN EVENT BROKER TO
MODULARIZE YOUR APP

130. TRACK BUG & GET METRICS

131. CAREFUL USE OF DARK MAGIC

132. DON’T BE THAT GUY

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

134. DO NOT CREATE MONSTERS

135. GIVE A TRY TO TECHNOLOGY

136. FOCUS ON YOUR ADDED VALUE

137. CLEVER
CLOUD
5 YEARS OLD EXPERIMENT

138. ARCHITECTURE
OVERVIEW

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

140. EXEMPLE ON CLEVER
CLOUD LOGS
MANAGEMENT

141. ELK
STACK

142. LOGSAPI
SIMPLE PROXY FOR ELASTICSEARCH

143. REWRITE LOGS API
logstash
ElasticSearch
Logs API

144. PROBLEMS
• Increasing load on ES
• No real time logs

145. PROBLEMS

146. REWRITE LOGS API
logstash
RabbitMQ
ElasticSearch
Logs API

147. JUST DO IT

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