Ocelot VS Refit

Sounds like you need some kind of ETL. The only dotnet library I know, which supports request aggregation, is Ocelot (https://github.com/ThreeMammals/Ocelot). But I doubt it is the only one out there.

They seems to recommend https://github.com/ThreeMammals/Ocelot

Ocelot Github Nuget: Install-Package Ocelot -Version 17.0.0

Ok, now that you created you Web API, it's time to work on your API Gateway. Start by adding the Ocelot package to your Gateway project:

Discovered Ocelot and it looks like a good place to start, so you have any thoughts on that?

I'd look for an open-source gateway using the programming language that you're familiar with. I was working multiple times with the custom API GW (including building my own for fun), and if you're familiar e.g. with C# take a look at this one https://github.com/ThreeMammals/Ocelot or even better https://github.com/microsoft/reverse-proxy If you need to build something really custom, there's a small chance that you will find a plug & play solution.

Lol, i guess your answer explains a lot about relevant knowledge into web architecture

Eg. Ocelot - https://github.com/ThreeMammals/Ocelot

A lot of people have given you good replies, but have you looked at Refit?

Another question that rises is, would it be better to use some HttpClient package to handle the requests, like Refit in combination with Polly. But then again, it seems Refit also uses the HttpClient factory, which was a bad thing according to the previous?

Define a Refit client interface with the following for each API endpoint, e.g. GET /foo:

Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.

Refit - simple, typed REST clients: https://github.com/reactiveui/refit

I'd advise using this https://github.com/reactiveui/refit tool for HTTP requests. It saves a lot of time for serialization, deserialization and exception handling.

Use Refit, and let manage the live of HttpClient. Also, Refit will give you a strongly typed client around an API. All you have to write is the interface. Ain't that neat ? If you can't, use the HttpClientFactory to create the HttpClient instance: https://learn.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/use-httpclientfactory-to-implement-resilient-http-requests

Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.

The controller is simple and use the Refit library to abstract the PokéAPI call and then, returns the data.

To be fair, Refit is pretty great.