Development Principles & Philosophy
•
5 gostaram•11,716 visualizações
Slides from the talk I gave at Web2Day/Tech2Day 2015. Principles and philosophy guides our developer lives at Redsmin, Bringr and now iAdvize. Here is what we've learn in the past 3 years working in startup environments, the ideas shared behind this talk are language and paradigm agnostic. Recording (in french): https://www.uslide.io/presentations/Aw6sX5ug-Tfzw5rNXAmdJg
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (19)
Semelhante a Development Principles & Philosophy
Semelhante a Development Principles & Philosophy (20)
Mais de François-Guillaume Ribreau
Mais de François-Guillaume Ribreau (12)
Último
Último (20)
Development Principles & Philosophy
- 3. Bringr
- 5. Bringr Leader européen de l'engagement client en temps réel. (click2chat, click2call, click2video, community, ...) #sold
- 6. Bringr
- 7. Developer oriented real-time monitoring and administration service for Redis
- 8. @FGRibreau COMPUTER SCIENCE IS ABOUT TRADEOFFS
- 9. @FGRibreau VS WHEN YOU FIGHT TO SURVIVE BETTER CHOOSE THE RIGHT PATH
- 10. @FGRibreau How can I make the right choice while coding?
- 11. @FGRibreau EASY.
- 13. @FGRibreau
- 15. SEPARATION OF CONCERNS @FGRibreau A.K.A THINK ABOUT ____#ROLES
- 18. Use the Separation of Concerns Luke! Morpheus (not sure about this one)
- 19. @FGRibreau Bringr Bringr Strategy Bringr Impact Bringr ... Bringr Sourcing Bringr ... Bringr Alerts
- 22. @FGRibreau Bringr Strategy Bringr Impact Bringr Backend .... Bringr Sourcing Bringr Account ... Bringr Alerts
- 23. @FGRibreau Bringr Strategy Bringr Impact Bringr Backend .... Bringr Sourcing Bringr Account ... Bringr Alerts Filtering Statistics Rules EnginePublishing Statistics Updater UIUIUI Indexing G+ Vimeo Facebook Youtube Wordpress Twitter Notifications ... ... ...
- 25. @FGRibreau “DIVIDE MICROSERVICES BETWEEN ACTIVE AND PASSIVE ONES
- 26. @FGRibreau MICROSERVICE TYPE DEFINITION ACTIVE ACT ON SOMETHING PASSIVE REACT TO SOMETHING
- 27. @FGRibreau MICROSERVICE TYPE e.g. IN THE ASYNC WORLD ACTIVE PUBLISHER PASSIVE CONSUMER #AMQP #RabbitMQ
- 28. @FGRibreau THE LESS ACTIVE ONES, THE BETTER
- 29. @FGRibreau THE LESS ACTIVE ONES, THE BETTER THE MORE PASSIVE ONES, THE BETTER
- 31. @FGRibreau “DIVIDE STATE AND LOGIC INSIDE MICROSERVICESMICROSERVICES
- 32. @FGRibreau “DIVIDE STATE AND LOGIC INSIDE MICROSERVICESCOMPONENTS
- 33. @FGRibreau My Worker My Worker My Worker State Repository #atomic #concurrency #resilient #scaleOut
- 34. @FGRibreau State Repository #parallelism #resilient #scaleOut State Repository My Worker A My Worker B
- 35. @FGRibreau EACH MICROSERVICE SHOULD HAVE ITS OWN RESPONSIBILITY
- 36. @FGRibreau EACH MICROSERVICE SHOULD HAVE ITS OWN RESPONSIBILITY limit bug domain
- 37. @FGRibreau EACH MICROSERVICE SHOULD HAVE ITS OWN RESPONSIBILITY limit bug domain clear contracts
- 38. @FGRibreau EACH MICROSERVICE SHOULD HAVE ITS OWN RESPONSIBILITY limit bug domain clear contracts easier scaling
- 39. @FGRibreau EACH MICROSERVICE SHOULD HAVE ITS OWN RESPONSIBILITY limit bug domain improved velocity clear contracts easier scaling
- 41. @FGRibreau “FAIL FAST, FAIL OFTEN
- 42. @FGRibreau crash process as soon as possible log errors restart process alert developer
- 43. @FGRibreau (NodeJS) process ramcpu I/O OS fail fast, fail often
- 44. @FGRibreau (NodeJS) process ramcpu I/O OS fail fast, fail often CPU, RAM and I/O are limited NodeJS process can’t always monitor himself
- 46. @FGRibreau WE DO WANT CONSTRAINTS No more than 90% CPU during X mins
- 47. @FGRibreau WE DO WANT CONSTRAINTS No more than 90% CPU during X mins No more than 512Mo of RAM during X mins
- 49. @FGRibreau “EVERYTHING SHOULD BE LIMITED IN BOTH SPACE & TIME
- 50. @FGRibreau NodeJS process ramcpu I/O OS fail fast, fail often
- 51. @FGRibreau NodeJS process ramcpu I/O OS fail fast, fail often Supervisor
- 52. @FGRibreau NodeJS process ramcpu I/O OS fail fast, fail often Supervisor limited in space & time
- 54. @FGRibreau NodeJS process dev staging prod CONFIGURATION MANAGEMENT
- 55. @FGRibreau // config.js module.exports = function(){ switch(process.env.NODE_ENV){ case 'development': return {dev setting}; case 'production': return {prod settings}; default: return {error or other settings}; } };
- 56. @FGRibreau app.configure('development', function(){ app.set('configPath', './confLocal'); // “./confLocal” is a constant }); app.configure('production', function(){ app.set('configPath', './confProduction'); // “./confProduction” is a constant });
- 57. @FGRibreau NodeJS process dev staging prod SHOULD MY PROCESS KNOW ITS OWN CONFIGURATION?
- 58. NOPE.
- 60. @FGRibreau constants files environment variables distributed Simplicity Genericity Knowing every running environments One configuration to rule them all CONFIGURATION
- 62. @FGRibreau “EVERY CONSTANT NUMBER, BOOLEAN OR STRING* SHOULD BE CONFIGURABLE
- 63. @FGRibreau var env = require('common-env')(logger); var config = env.getOrElseAll({ amqp: { login: 'guest', password: 'guest', host: 'localhost', port: 5672, reconnect: false } }); var conn = require('amqp').createConnection(config.amqp); AMQP_LOGIN="user" AMQP_PASSWORD="azerty" node server.js npm install common-env https://github.com/FGRibreau/common-env
- 65. @FGRibreau But my cloud provider uses AMQP_ADDON_LOGIN what should I do?
- 66. @FGRibreau ? var config = env.getOrElseAll({ amqp: { addon:{ login: 'guest', password: 'guest', host: 'localhost', port: 5672, reconnect: false } } }); var conn = amqp.createConnection(config.amqp.addon);
- 67. @FGRibreau
- 68. NOPE.
- 70. @FGRibreau NodeJS processLauncher SoC env. vars. Internal code is dependent from external naming convention
- 71. @FGRibreau var config = env.getOrElseAll({ amqp: { login: { $default: 'guest', $aliases: ['AMQP_ADDON_LOGIN'] }, password: 'guest', host: 'localhost', port: 5672, reconnect: false } }); var conn = amqp.createConnection(config.amqp);
- 73. // /config.js var logger = require('my-logger').createLogger(); var env = require('common-env')(logger); module.exports = env.getOrElseAll({ amqp: { login: 'guest' // ... } }); // /app.js var config = require('./config'); // /src/my/own/module.js var config = require('../../../config');
- 75. NOPE.
- 76. var logger = require('my-logger').createLogger(); var env = require('common-env')(logger); module.exports = env.getOrElseAll({ amqp: { login: 'guest' // ... } }); /config.js
- 77. var logger = require('my-logger').createLogger(); var env = require('common-env')(logger); module.exports = env.getOrElseAll({ amqp: { login: 'guest' // ... } }); /config.js
- 78. var logger = require('my-logger').createLogger(); var env = require('common-env')(logger); module.exports = env.getOrElseAll({ amqp: { login: 'guest' // ... } }); /config.js
- 79. // config now asks for logger module.exports = function (logger) { var env = require('common-env')(logger); return env.getOrElseAll({ amqp: { login: 'guest' // ... } }); }; /config.js
- 80. // config now asks for logger module.exports = function (logger) { var env = require('common-env')(logger); return env.getOrElseAll({ amqp: { login: 'guest' // ... } }); }; /config.js // caller, must specify logger to use config // app.js var logger = require('my-logger').createLogger(); var config = require('./config')(logger);
- 81. HUM I THINK I KNOW THIS PRINCIPLE
- 82. @FGRibreau DEPENDENCY INVERSION This is the D from S.O.L.I.D:
- 84. // /app.js var config = require('./config')(logger); // /src/my/own/module.js var config = require('../../../config')(logger); ✘ DI ✘ DRY
- 85. // /app.js var config = require('./config')(logger); // /src/my/own/module.js module.exports = function (config) { }; ✔ DI ✔ DRY
- 86. HUM, LET CREATE US A REMINDER
- 87. @FGRibreau “”../“ IS A CODE SMELL
- 89. @FGRibreau CRON
- 90. @FGRibreau CRON
- 91. #USERS
- 92. CRON IS NOT WORKING ANYMORE
- 93. #YOU
- 94. @FGRibreau CRON
- 95. @FGRibreau CRON
- 96. #USERS
- 97. CRON IS NOT WORKING ANYMORE
- 98. #YOU
- 99. @FGRibreau
- 100. @FGRibreau Process (e.g. cron) ramcpu I/O OS
- 101. @FGRibreau server Process (e.g. cron) ramcpu I/O OS Supervisor
- 102. @FGRibreau
- 103. @FGRibreau ?
- 104. @FGRibreau ?
- 107. @FGRibreau “I SHOULD ALWAYS BE PROACTIVELY ALERTED
- 110. @FGRibreau “DIVIDE MICROSERVICES BETWEEN ACTIVE AND PASSIVE ONES
- 111. @FGRibreau “DIVIDE STATE AND LOGIC
- 112. @FGRibreau “EVERYTHING SHOULD BE LIMITED IN BOTH SPACE & TIME
- 113. @FGRibreau “EVERY CONSTANT NUMBER, BOOLEAN OR STRING* SHOULD BE CONFIGURABLE
- 114. @FGRibreau “”../“ IS A CODE SMELL
- 115. @FGRibreau “I SHOULD ALWAYS BE PROACTIVELY ALERTED
- 117. @FGRibreau THE MOST IMPORTANT PRINCIPLE BEING
- 120. @FGRibreau PRINCIPLE Code dependencies should always be up-to-date
- 121. @FGRibreau AUTOMATION Build should break if code dependencies are not up-to-date
- 122. @FGRibreau PRINCIPLE Code style should always be consistent
- 123. @FGRibreau AUTOMATION Run a style-checker at each build
- 124. @FGRibreau PRINCIPLE Every developers should follow D.R.Y. (Don’t Repeat Yourself)
- 125. @FGRibreau AUTOMATION Run a structural code similarities tool at each build
- 126. @FGRibreau HERE IS WHAT WE DID
- 128. ONE LAST THING
- 135. Follow me @FGRibreau Questions? Join us @iAdvize! Thank you!