Cloud Native Java
summary
A runnable reservation service is created with Spring Boot, H2 and JPA and exposed via Spring Data REST; configuration moves to a Git-backed Spring Cloud Config server with live refresh. Services register to Eureka + Zuul + Ribbon for discovery and client-side load balancing; an edge API Gateway transforms JSON to a simple name list. Resilience uses Hystrix circuit breaker with a fallback that returns an empty list, Zipkin collects distributed traces (example request ≈18 ms), and RabbitMQ is wired for streaming.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:09About Josh
- 3:30Bounded Context
- 8:47Systems are Hard
- 11:32Nan Choices
- 12:32JAR
- 16:32API
- 18:32Config Server
- 20:32Setup Config Server
- 24:32Config Refresh
- 30:32Zool
- 34:32Mediation
- 36:32Type Tokens
- 38:32Reactive Concurrent
- 40:32Circuit Breaker
- 42:32Graceful Degradation
- 44:32Distributed Tracing
- 46:32Distributed Tracing Demo
- 48:32Summary








