Microservices - Testing Microservices
You want to design a chaos engineering experiment to test how your microservices handle database latency spikes. Which approach best fits this goal?
You want to design a chaos engineering experiment to test how your microservices handle database latency spikes. Which approach best fits this goal?
hard📝 Trade-off Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Understand the goal of testing database latency spikes
The goal is to see how microservices behave when database responses are slow.Step 2: Choose the best chaos experiment approach
Injecting artificial latency simulates slow database calls directly, matching the goal.Step 3: Evaluate other options
Killing instances tests availability, not latency; increasing replicas without testing doesn't simulate latency; disabling monitoring hides important data.Final Answer:
Inject artificial latency into database calls during tests -> Option AQuick Check:
Test latency by injecting delays = Inject artificial latency into database calls during tests [OK]
Quick Trick: Inject delays to test latency, not kill instances [OK]
Common Mistakes:
- Confusing instance failure with latency testing
- Adding replicas without testing effects
- Turning off monitoring during chaos
Master "Testing Microservices" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes