Web API One Point Connection Approach.( One web -api object will created for severing multiple Business needs)

Certified Lead Developer

Hi All,

I could would like to your opinion on the two different approach which we drafted. Need to understand the pros and cons 

Approach1:

 

We are creating one webapi and based on the path parameter it will be routed to respective Handler(expression rule)and the handler will respond back 

Question:

1. Creating One web-API /per http method ,will it create high load to Web-api which will in turn make 503 exception(timeout) on prod?

Approach 2:

Creating a Web-API /per Package and which in turn as respective handler (expression rule ) for the response

Question:

1)desired approach to solve the needful?

2)Pros and cons on Approach 1 over the Approach 2?

Thanks in advance!

  Discussion posts and replies are publicly visible

Parents
  • Both will work to meet your use case.

    The pros of having one API object for each method is that you can separately secure each method with different security. If you put everything in one endpoint then you can only secure that one endpoint using group security. Also, if each method has a different request type (GET, PUT) then you will need a separate object for each.

    If your logic is simple, I think having one web API object could add simplicity to your application. Otherwise, create multiple objects.

Reply
  • Both will work to meet your use case.

    The pros of having one API object for each method is that you can separately secure each method with different security. If you put everything in one endpoint then you can only secure that one endpoint using group security. Also, if each method has a different request type (GET, PUT) then you will need a separate object for each.

    If your logic is simple, I think having one web API object could add simplicity to your application. Otherwise, create multiple objects.

Children