API Gateway issue about netcoremicroservicessample HOT 6 CLOSED

You are absolutely right.
I started looking into Kong and Tyk and realized they offer a community edition (free) and a premium version (paid).

I'll look into improving the Api gateway with Ocelot.

from netcoremicroservicessample.

Normally I'd go with a fully managed API gateway on AWS, Azure, etc.
Right now I'm looking at Kong and Tyk

from netcoremicroservicessample.

I think there could be a couple of issues.

Here https://github.com/madslundt/NetCoreMicroservicesSample#consul you mention that the API Gateway uses Consul, though in the appsettings.json there is no Consul options.

I also noticed that there is no configure method, there is no app.UseConsul().

No link to Consul in the docker compose for the API Gateway.

from netcoremicroservicessample.

Thank you for reporting this.

I'm looking to replace the api gateway with something that also integrates better with Swagger

from netcoremicroservicessample.

Anything in particular that you are looking at so far?

from netcoremicroservicessample.

Not sure if you're looking for others opinions, but I for sure would prefer Ocelot as it is completely free and you can implement anything with it rather than using paid plugins .etc

from netcoremicroservicessample.