Apigee X Target endpoints limit

[venkateshwargan]

Hi Team,

I have a requirement to create an Apigee API proxy for the below endpoints.

POST https://<host>/order-mgmt/orders

PUT https://<host>/order-mgmt/orders/{order-id}

DELETE https://<host>/order-mgmt/orders/{order-id}

GET https://<host>/order-mgmt/orders/{order-id}

I have listed one use case above for which I have created two endpoints, one endpoint for POST and a second endpoint for (GET, PUT, and DELETE), similarly, I have 500 use cases, which means 500*2(Target endpoints) then there will be more than 1000 endpoints.

Are there any limitations on the number of Apigee X target endpoints? 

are there any issues with the below approach accommodating all order functionalities in a single endpoint? I know ** means it can accept everything after orders and also it will be a little difficult to debug the issues. Please let me know your thoughts on this also is there any limitations on the number of target endpoints/

<Flow name="Orders">

 <Description/>

 <Request/>

 <Response/>

 <Condition>proxy.pathsuffix MatchesPath "/orders**</Condition>

</Flow>

<RouteRule name="Orders">

 <TargetEndpoint>Orders</TargetEndpoint>

 <Condition>proxy.pathsuffix MatchesPath "/orders**</Condition>

</RouteRule> 

Target endpoint:

<TargetEndpoint name="Orders">

     <PreFlow name="PreFlow">

        <Request>

        </Request>

        <Response/>

    </PreFlow>

    <Flows/>

    <PostFlow name="PostFlow">

        <Request/>

        <Response/>

    </PostFlow>

    <HTTPTargetConnection>

        <LoadBalancer>

<Server name="ts-order-services"/>

</LoadBalancer>

<Path>/order-service/v1/{proxy.pathsuffix}</Path>         

    </HTTPTargetConnection>

</TargetEndpoint>