Investigate impact and possibilities of an Ocelot API Gateway solution
Open
Investigation
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
At this moment the api-gateway has been implemented as a microservice with some internal checks and message aggregation of the replies from different micro-services.
Ocelot might be a possibility to simplify the codebase, and achieve the same results.
In this investigation, determine the impact of refactoring to Ocelot and if it indeed brings advantages.
The second question in this case, is if the APIGateway pattern is in the current implementation according to the principles of the pattern (is it doing, what it should be doing).
Outcome: Architectural Decision Record; Possibly proof-of-concept
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.