Key Problems of Microservice Architecture
summary
A small demo system implements three services (challenge, indexer, user) on Hazelcast and uses Netflix OSS: Eureka discovery + Ribbon client-side load balancing, Archaius for dynamic config, and Hystrix circuit breaker with fallback queue plus RxJava commands. The presenter shows killing service instances, Hystrix opening the circuit, queued index requests being replayed on recovery, and metrics in the dashboard. Notes: Netflix runs ~600 microservices and Amazon pages call 100–150 services.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:57Monolith problems
- 5:22What is a service
- 10:21Service config & discovery
- 17:11Twitter microservices examples
- 22:41Service operation demo
- 37:46Service autonomy & error handling
- 44:31Circuit Breaker pattern
- 51:20Network interaction problems
- 1:00:08Choosing microservices
related talks
49mChallenges in Implementing Microservices
53mBooting your micro-services architecture with Spring and Netflix
48mChallenges in Implementing MicroServices
50mMicroservices Design Patterns for Java Application
50mMicroservices for Mortals
23mMicroservices – Diptanu Choudhury
40mCloud Native Java
24mDistant Past of Microservices
