What are Ocelot configuration and routing limitations?

[SheruGaur]

Hi,

We are internally doing a POC on ocelot as API Gateway in our organisation.

While we really like the product till now, we had few basic queries. we didnt find much in documentation or the issues and discussion.

If someone from their experience can share some info on following it will be helpful.

1. How many maximum routes can be configured in Ocelot.Json?
2. Any limitations for define maximum routes in configuration file?
3. Any standard configuration for which this has been tested?
4. in case of multiple configuration files, does Ocelot allow the change in individual config files to be updated in the merged ocelot.json at runtime?
5. Do we need to create an ocelot.global.json file for where multiple config files configuration to work?

Pls help with any references...

Thanks
Sheru

[raman-m]

@ks1990cn Tanmay, please help!
I believe you will explain to Mr. Sheru Ocelot Configuration feature, and answer on these questions better than me.

[SheruGaur]

@ks1990cn Hi Tanmay, take your time but provide the prior solution for my raise queries.

[ks1990cn]

I am trying to replicate it, meanwhile look at https://stackoverflow.com/questions/67057050/cannot-merge-ocelot-config-files

[SheruGaur]

@ks1990cn Still waiting for your reply.

[ks1990cn]

You tried this solution?

[SheruGaur]

Yes, but it is not working when any configuration change on the fly

[ks1990cn]

Hi @SheruGaur ,

Here are your answers:

1.) There is no maximum limit for routes you can define in Ocelot.Json. Internally code to uses simply list public List Routes { get; }. Just having huge number of routes with heavy configuration may impact startup/ search time for downstream route mapping. But I am pretty sure It can handle thousands / Lakhs without much impact on startup/map to downstream route.

2.) No there is no limit.

3.) There are few samples you can refer for what you are looking for, every where its tested ok. Ocelot have nice standards for test cases.
https://ocelot.readthedocs.io/en/latest/
https://learn.microsoft.com/en-us/dotnet/architecture/microservices/multi-container-microservice-net-applications/implement-api-gateways-with-ocelot
You can discuss with us, we can help you in understanding things you need.

[raman-m]

Thank you!

[SheruGaur]

thanks @ks1990cn. for providing the suggestions but still I am waiting for answer point no. 4th and 5th. Also, I want to know about the highest hardware configuration for ocelot Api gateway setup?

Thanks

[raman-m]

The hardware configuration can be the same as for regular ASP.NET Core 7+ web app. No limits!
It is better to think in terms of Requests per second... and scalability... Hardware requirements are vertical scalability!
It is better to focus on horizontal scalability!... On Kubernetes and a cloud...
So, you should think in terms of Kubernetes and regular Docker container hardware requirements.