Build Microservices with Node.js, Dublin

Two days of training to master microservices with Node.js.

_

Delivered by the expert instructors of RisingStack.

Czibik Peter Gergely Nemeth Tamas Kadlecsik

Peter Czibik, Gergely Nemeth & Tamas Kadlecsik

Tickets

Register interest

Additional Information

This course is for you if

  • you are considering microservices for your organization,
  • you want to understand microservices better,
  • you want to migrate to microservices,
  • you want hands-on experience in building microservices with Node.js.

Prerequisites

  • Prior Javascript and Node.js experience is nice to have. You will understand the coding part a lot easier, as we won't go into the basics of Node.js

  • No prior experience with microservices is required - we will cover everything you need to get started.

The exact location of the venue in Dublin will be announced later.

Course outline

Day One:

1. Microservices architecture in the company

  • Monolith applications
  • Microservices
  • Organizational effect
  • Decentralized Data Management
  • Comparison to Service Oriented Architecture (SOA)
  • Comparison to Self-Contained Systems (SCS)

2. Services and teams

  • Granularity of a service
  • Service communication
  • API versioning and routing
  • Service discovery techniques
  • Automation and microservices
  • Service bootstrapping
  • Service principles and best practices

3. Moving to microservices

  • When not to choose microservices?
  • When is it too early?
  • Evolutionary design
  • Proxy approach
  • Direct Client‑to‑Microservices Communication
  • API Gateway
  • Security

4. Architectural patterns in distributed systems

  • Idempotency
  • Data models
  • Microservices anti-patterns
  • Event driven microservices
  • CQRS (Command Query Responsibility Segregation)
  • Event Sourcing

Day Two:

5. Caching

  • Caching microservices
  • Stale caching
  • Failover caching
  • Caching with response headers
  • Multi-level caching
  • LRU algorithm
  • LFU algorithm

6. Reliability in microservices

  • Reliability indicators: SLI, SLO, SLA
  • Error Budget
  • Cost of nines
  • Risk of the microservice architecture
  • Graceful degradation
  • Failover caching
  • Change management
  • Health-check and load balancing
  • Self-healing
  • Retry logic
  • Fail fast
  • Circuit breakers
  • Rate limiters and load shedders
  • Testing for failures

7. Testing microservices

  • Local development
  • Testing in microservices
  • Unit testing
  • Contract testing
  • Integration tests
  • E2E testing
  • UI Testing

8. Debugging and monitoring microservices

  • Logging in a distributed system
  • Distributed Tracing
  • Monitoring Microservices