grpc-ecosystem / grpc-ecosystem/grpc-spring
A service registers multiple instances on consul through coding. Why can grpc only call the service configured in the configuration file.
Open
question
- Dominant language
- Java
- Stars
- 3.7k
- Forks
- 858
- PR merge metrics
- No merged PRs in 30d
Description
A service registers multiple instances on consul through coding. Why can grpc only call the service configured in the configuration file.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reproducing the difference between programmatic Consul registration and the configured service, then trace the grpc-spring service-discovery path. Done means the cause is explained and the supported way to call the registered instances is documented or identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java, spring-boot
- Domain
- backend-api-design, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100