resource path limit

Is there any upper limit on the number of resource paths can be defined in a proxy?

0 5 275
5 REPLIES 5

Not applicable

Hi,

I don't think there is any limit to the resource path.

Having said that, you want to keep it less than 5 so that the consumer doesn't get lost inbetween.

I mean,

/<base_path>/customers/accounts/orders/orderlines

looks like the most that you should use considering all the resources are operational (exposed as APIs).

@Mahammad Feroz There is no limit on the number of resource paths you configure within an API proxy. However there are guidelines & best practices on how to build proxies in Edge... see here.

@Ravi Shah, my query is on the number of resource path(s) in a proxy but not number of resources in a single path.

e.g:

/<base_path>/customer

/<base_path>/customer/address

/<base_path>/accounts/transactions

/<base_path>/accounts/transfer

/<base_path>/orders/orderlines

Thanks for clarifying @Mahammad Feroz As I indicated above there is no limit on the number of end points (resource paths) that you can configure within an API proxy.

Thanks for the clarification @Mohammad Feroz,

My comments apply to the horizontal as well as vertical resource model for the APIs. Hence, I really suggest you to keep it to a controllable limit to help your app developers easily adapt your APIs.