🎤 Microservice Architecture with Reusable Components
- 👤 Nikita Galkin
- Twitter: @galk_in
- Web: http://galk.in/
📹
Video:
https://youtu.be/2NoDBZogRFI
DRY (Don’t repeat yourself) is the most frequently violated principle in microservices. For avoiding this issue you can use reusable components, private npm packages for example. Best practices what will help you to achieve this are ECB (entity, control, boundary) pattern, 12 factor manifest, code generation. In our project we use technical stack based on Node.js, Docker, RabbitMQ, but ideas from this talk can be used for any microservice's technical stack
This page was generated from this YAML file. Found a typo, want to add some data? Just edit it on GitHub.