De slides van collega Stefan Pante op de Node.js User Group Belgium meetup (http://www.meetup.com/DigAnt-Cafe/events/229507635/)

1. Stefan Pante
@stefanpante

2. Node.js at Digipolis:
Experiences and lessons learned
24/03/2016

3. The Node.js Team

4. A-stad

5. Stack

6. A-profiel (user app)
melding
en
e-loket
notificati
on
redactie ...
helpcent
er
cart
(betalen)
search
stadspla
n
Civilian/Employee

7. Centrale Reference Systems
A-profiel (user app)
melding
en
e-loket
notificati
on
redactie ...
helpcent
er
cart
(betalen)
search
stadspla
n
Civilian/Employee

8. Good Ideas
1. Reusable modules

9. Good Ideas
1. Reusable modules
2. Basic application structure

10. Good Ideas
1. Reusable modules
2. Basic application structure
3. Code Quality

11. 1. Reusable modules

12. New Application
User Service
Apache Solr
Notification Service

13. Modules
● Communication and Authorization

14. Modules
● Communication and Authorization
● Common tasks: mailing, response handling…

15. Modules
● Communication and Authorization
● Common tasks: mailing, response handling…
● Wrapper around existing modules, with specific
configuration

16. Astad module was born

17. All dependencies
you’d ever need

18. Everything initialised and
exposed on Express app

19. Disadvantages
● Hard to maintain (versioning difficult)

20. Disadvantages
● Hard to maintain (versioning difficult)
● Many unused dependencies

21. Disadvantages
● Hard to maintain (versioning difficult)
● Many unused dependencies
● Scripts, cron jobs…

22. Disadvantages
● Hard to maintain (versioning difficult)
● Many unused dependencies
● Scripts, cron jobs…
● Required intrinsic knowledge

25. Astad Module

26. Astad Module
Astad-Solr Astad-User Astad-Request ...

27. Many modules were created

28. Only use what you need,
Dependencies are explicit!

29. Easier to test!
Each module = one concern

30. Disadvantages
● Still cumbersome to update dependencies
with git tags

31. Disadvantages
● Still cumbersome to update dependencies
with git tags
● BUG = Manually updating package.json of
dependents

32. (Sinopia)

33. Our very own private NPM
repository

34. ~ Allows patch variations

35. 2. Basic application structure

36. Basic application structure
● Quickly start developing

37. Basic application structure
● Quickly start developing
● Uniformity and familiarity

38. Skeleton app
● Git repository to fork

39. Skeleton app
● Git repository to fork
● Basic uniform file structure

40. Skeleton app
● Git repository to fork
● Basic uniform file structure
● Most used modules included

41. Disadvantages
● Still some basic configuration required

42. Disadvantages
● Still some basic configuration required
● Some apps need frontend, others don’t

43. Disadvantages
● Still some basic configuration required
● Some apps need frontend, others don’t
● Need to remove unused dependencies

45. Yeoman Generator(s)
● Asks basic questions

46. Yeoman Generator(s)
● Asks basic questions
● Conditionally load dependencies,
file structure

47. Yeoman Generator(s)
● Asks basic questions
● Conditionally load dependencies,
file structure
● Basic config taken care of

48. yo astad
Please specify your project name: “A-stad”
Do you need a frontend for this project : (Y/n) “Y”

51. 3. Code quality

52. Testing
● Ensure functionality is correct

53. Testing
● Ensure functionality is correct
● Test robustness of methods

54. Testing
● Ensure functionality is correct
● Test robustness of methods
● Tests allow refactoring

56. Testing without Control
● Easy to cheat

57. Testing without Control
● Easy to cheat
● Tests are neglected

58. Automated testing
● No deploys without tests
● PR’s are not approved when tests fail

59. Other measures
● Coding guidelines:JSLint, ESLint
● Code Reviews during PR, min 2 other dev’s.

60. Conclusion
● Reusable modules
● Basic application structure
● Code Quality

61. Conclusion
Learning from your mistakes allows for continuous
improvement and enables you to write better code.

62. Questions?