Bird
0
0

A developer notices that Netflix microservices are tightly coupled, causing deployment issues. What is the best fix?

medium📝 Analysis Q14 of 15
Microservices - Real-World Architecture Case Studies
A developer notices that Netflix microservices are tightly coupled, causing deployment issues. What is the best fix?
AIncrease the database size to handle more data
BRefactor services to communicate only via APIs and avoid direct calls
CUse shared global variables for communication
DMerge all microservices into one big service
Step-by-Step Solution
Solution:
  1. Step 1: Identify tight coupling problem

    Tightly coupled services depend directly on each other, causing deployment and scaling problems.
  2. Step 2: Apply microservice best practice

    Services should communicate only via APIs to remain independent and deploy separately.
  3. Final Answer:

    Refactor services to communicate only via APIs and avoid direct calls -> Option B
  4. Quick Check:

    Loose coupling via APIs fixes deployment issues [OK]
Quick Trick: Use APIs to keep services independent and deployable [OK]
Common Mistakes:
  • Merging services defeats microservice benefits
  • Using shared variables breaks isolation
  • Increasing DB size doesn't fix coupling

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes