Active health checks for statically defined API services
Open
Nobody has claimed this yet.
enhancement
High Availability
Priority: Medium
size/L
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Wednesday Sep 05, 2018 at 13:24 GMT
Originally opened as https://github.com/gizafoundation/api-layer/issues/89
As Sherman, I would like API layer to display service status in the API catalog based on the availability of the APIs and route only to active instances
Notes:
- Done in our Discovery Service instead of the service sending status to Eureka
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Discovery Service behavior described in the notes and how the API catalog receives service availability information. Confirm whether active-instance routing and status display are already handled there rather than by services reporting to Eureka; done would mean both catalog status and routing reflect API availability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100