Download as PDF, PPTX
![@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);](https://image.slidesharecdn.com/keynote-pourexportpdf-150625124219-lva1-app6892/85/Development-Principles-Philosophy-71-320.jpg)
![@FGRibreau
“[add your own]...](https://image.slidesharecdn.com/keynote-pourexportpdf-150625124219-lva1-app6892/85/Development-Principles-Philosophy-116-320.jpg)
Uploaded byFrançois-Guillaume Ribreau
Development Principles & Philosophy
The document outlines development principles and philosophies by François-Guillaume Ribreau, emphasizing the importance of separation of concerns, microservice design, failure management, and configuration management. Key principles include proactive alerts, limiting resources, and ensuring code dependencies and style consistency. It concludes with a reminder to not establish unenforceable conventions in development practices.
More Related Content
![[BreizhCamp, format 15min] Construire et automatiser l'ecosystème de son Saa...](https://cdn.slidesharecdn.com/ss_thumbnails/20170418construireetautomatiserlecosystemedesonsaasgraceaunespecificationswagger-170426174720-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Development Principles & Philosophy
![[BreizhCamp, format 15min] Une api rest et GraphQL sans code grâce à PostgR...](https://cdn.slidesharecdn.com/ss_thumbnails/20170418uneapirestetgraphqlsanscodegraceapostgrestsub0etpostgresql-170426174719-thumbnail.jpg?width=640&height=640&fit=bounds)
Development Principles & Philosophy
- 1.
- 2.
- 3.
- 4.
- 5. Bringr Leader européen de l'engagementclient en temps réel. (click2chat, click2call, click2video, community, ...) #sold
- 6.
- 7. Developer oriented real-time monitoringand administration service for Redis
- 8. @FGRibreau COMPUTER SCIENCE IS ABOUTTRADEOFFS
- 9. @FGRibreau VS WHEN YOU FIGHTTO SURVIVE BETTER CHOOSE THE RIGHT PATH
- 10. @FGRibreau How can Imake the right choice while coding?
- 11.
- 12.
- 13.
- 14.
- 15. SEPARATION OF CONCERNS @FGRibreau A.K.A THINKABOUT ____#ROLES
- 16.
- 17.
- 18. Use the Separationof Concerns Luke! Morpheus (not sure about this one)
- 19.
- 20.
- 22. @FGRibreau Bringr Strategy BringrImpact Bringr Backend .... Bringr Sourcing Bringr Account ... Bringr Alerts
- 23. @FGRibreau Bringr Strategy BringrImpact 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 ACTIVEAND PASSIVE ONES
- 26. @FGRibreau MICROSERVICE TYPE DEFINITION ACTIVEACT 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 ACTIVEONES, THE BETTER
- 29. @FGRibreau THE LESS ACTIVEONES, THE BETTER THE MORE PASSIVE ONES, THE BETTER
- 31. @FGRibreau “DIVIDE STATE ANDLOGIC INSIDE MICROSERVICESMICROSERVICES
- 32. @FGRibreau “DIVIDE STATE ANDLOGIC INSIDE MICROSERVICESCOMPONENTS
- 33. @FGRibreau My Worker MyWorker 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 HAVEITS OWN RESPONSIBILITY
- 36. @FGRibreau EACH MICROSERVICE SHOULD HAVEITS OWN RESPONSIBILITY limit bug domain
- 37. @FGRibreau EACH MICROSERVICE SHOULD HAVEITS OWN RESPONSIBILITY limit bug domain clear contracts
- 38. @FGRibreau EACH MICROSERVICE SHOULD HAVEITS OWN RESPONSIBILITY limit bug domain clear contracts easier scaling
- 39. @FGRibreau EACH MICROSERVICE SHOULD HAVEITS OWN RESPONSIBILITY limit bug domain improved velocity clear contracts easier scaling
- 40.
- 41.
- 42. @FGRibreau crash process assoon as possible log errors restart process alert developer
- 43. @FGRibreau (NodeJS) process ramcpu I/O OS failfast, fail often
- 44. @FGRibreau (NodeJS) process ramcpu I/O OS failfast, fail often CPU, RAM and I/O are limited NodeJS process can’t always monitor himself
- 45.
- 46. @FGRibreau WE DO WANT CONSTRAINTS Nomore than 90% CPU during X mins
- 47. @FGRibreau WE DO WANT CONSTRAINTS Nomore than 90% CPU during X mins No more than 512Mo of RAM during X mins
- 48.
- 49. @FGRibreau “EVERYTHING SHOULD BE LIMITEDIN BOTH SPACE & TIME
- 50. @FGRibreau NodeJS process ramcpu I/O OS failfast, fail often
- 51. @FGRibreau NodeJS process ramcpu I/O OS failfast, fail often Supervisor
- 52. @FGRibreau NodeJS process ramcpu I/O OS failfast, fail often Supervisor limited in space & time
- 54. @FGRibreau NodeJS process dev stagingprod 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 stagingprod SHOULD MY PROCESS KNOW ITS OWN CONFIGURATION?
- 58.
- 59.
- 60. @FGRibreau constants files environment variables distributed Simplicity Genericity Knowingevery running environments One configuration to rule them all CONFIGURATION
- 61.
- 62. @FGRibreau “EVERY CONSTANT NUMBER, BOOLEANOR 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
- 64.
- 65. @FGRibreau But my cloudprovider 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.
- 68.
- 69.
- 70. @FGRibreau NodeJS processLauncher SoC env. vars. Internalcode 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');
- 74.
- 75.
- 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 nowasks for logger module.exports = function (logger) { var env = require('common-env')(logger); return env.getOrElseAll({ amqp: { login: 'guest' // ... } }); }; /config.js
- 80. // config nowasks 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 IKNOW THIS PRINCIPLE
- 82. @FGRibreau DEPENDENCY INVERSION This is theD from S.O.L.I.D:
- 83.
- 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 CREATEUS A REMINDER
- 87. @FGRibreau “”../“ IS ACODE SMELL
- 88.
- 89.
- 90.
- 91.
- 92. CRON IS NOT WORKINGANYMORE
- 93.
- 94.
- 95.
- 96.
- 97. CRON IS NOT WORKINGANYMORE
- 98.
- 99.
- 100.
- 101. @FGRibreau server Process (e.g. cron) ramcpuI/O OS Supervisor
- 102.
- 103.
- 104.
- 105.
- 106.
- 107. @FGRibreau “I SHOULD ALWAYSBE PROACTIVELY ALERTED
- 108.
- 109.
- 110. @FGRibreau “DIVIDE MICROSERVICES BETWEEN ACTIVEAND PASSIVE ONES
- 111.
- 112. @FGRibreau “EVERYTHING SHOULD BE LIMITEDIN BOTH SPACE & TIME
- 113. @FGRibreau “EVERY CONSTANT NUMBER, BOOLEANOR STRING* SHOULD BE CONFIGURABLE
- 114. @FGRibreau “”../“ IS ACODE SMELL
- 115. @FGRibreau “I SHOULD ALWAYSBE PROACTIVELY ALERTED
- 116.
- 117.
- 118.
- 119.
- 120. @FGRibreau PRINCIPLE Code dependencies should alwaysbe up-to-date
- 121. @FGRibreau AUTOMATION Build should breakif code dependencies are not up-to-date
- 122. @FGRibreau PRINCIPLE Code style should alwaysbe consistent
- 123. @FGRibreau AUTOMATION Run a style-checkerat each build
- 124. @FGRibreau PRINCIPLE Every developers shouldfollow D.R.Y. (Don’t Repeat Yourself)
- 125. @FGRibreau AUTOMATION Run a structuralcode similarities tool at each build
- 126.
- 127.
- 128.
- 129.
- 130.
- 131.
- 132.
- 133.
- 134.
- 135. Follow me @FGRibreau Questions? Joinus @iAdvize! Thank you!