[Solved] You have this routing rule: route: path: /user service: user-service-v1 weight: 100 But requests to /user/profile are not reaching user-service-v1. What is the likely problem? | Microservices

Microservices - Service Mesh

You have this routing rule:

route:
  path: /user
  service: user-service-v1
  weight: 100

But requests to /user/profile are not reaching user-service-v1. What is the likely problem?

AService name is incorrect and causes failure

BWeight should be split between multiple services

CThe path rule matches only exact /user, not subpaths like /user/profile

DRouting rules cannot use path matching

Step-by-Step Solution

Solution:

Step 1: Analyze the path matching rule
The rule matches exactly /user, but /user/profile is a subpath and may not match unless wildcard or prefix matching is used.
Step 2: Identify why requests fail
Since /user/profile does not match exactly /user, requests do not route to user-service-v1.
Final Answer:
The path rule matches only exact /user, not subpaths like /user/profile -> Option C
Quick Check:
Exact path matching excludes subpaths [OK]

Quick Trick: Exact path matches exclude subpaths unless wildcard used [OK]

Common Mistakes:

MISTAKES

Master "Service Mesh" in Microservices

9 interactive learning modes - each teaches the same concept differently

More Microservices Quizzes

You have this routing rule: