This document discusses how Node.js can help address challenges with microservices architectures. It outlines common problems like logging, configuration, health checks, and common logic that must be addressed across microservices. Node.js solutions like common logging packages, tracing middleware, and process managers like PM2 are presented as ways to solve these problems by creating reusable components and standardizing infrastructure across services. Examples of implementing common logging and tracing are provided to illustrate how Node.js can help build more maintainable microservices applications.

1. NODE &
MICRO-SERVICES
MICHAEL HABERMAN
FREELANCER

2. AGENDA
• Challenges with micro-services code base
• How node may help

3. GENERAL MICRO-SERVICE ARCHITECTURE
Client
API Gateway
User service Purchase service Analytics service
Permission
service

4. QUICK LOOK AT OUR DEMO

5. CHALLENGES WITH CODE
• Small code
• A lot of infra:
• Logs / Tracing
• Configuration
• Health checks
• Process management
• Common logic (authentication) – package or a service?

6. CREATING COMMON LOGS
• Common logs:
• Centralized logs
• Formatted logs
• No need for special configuration
• Multiple outputs
• Many uses ELK stack (Elastic search, Log stash,
Kibana)

7. HOW TO: COMMON LOG
• Three options
• Every microservice implements log features
• Huge mess!!
• Log service
• Cons: lot of network, chances to failure, may impact performance
• Pro: Easier to deploy changes
• Common package (npm)
• Easy to implement and maintain

8. COMMON LOGS

9. COMMON LOGS
• Log separated into package
• Very simple to use
• One problem….
• commonLogger determine Winston version

10. PACKAGE PEER DEPENDENCIES
• NPM’s peer dependencies
Service A –Winston 2.3.1
CommonLogger
Winston >= 2.x.x

11. SEMANTIC VERSIONING
X.Y.Z
Bug fixNew featureBreaking change

12. COMMON PACKAGES – MUST HAVE
• Logs
• Express
• Health checks
• Correlation id (tracing)
• Configuration

13. TRACING
Client
API Gateway
Purchase service Analytics serviceUser service

14. TRACING
• Add custom HTTP header: x-correlation-id (some guid)
• Log the correlation id anytime
• Search by specific id while debugging
• Middleware is a great tool for the job

15. TRACING

16. NODE – PROCESS MANAGEMENT
• Restart on crash
• Don’t restart forever
• Use pm2 / forever

17. THANK YOU!
michael@haberman.i
o
@hab_mic

18. QUESTIONS?