[APIM] [C4] [2.1.0] API Gateways with Dedicated Back Ends

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[APIM] [C4] [2.1.0] API Gateways with Dedicated Back Ends

Akila Amarasinghe
Hi all,

WSO2 API manager currently provides the facility for the user to input a single endpoint to the API when designing it. So every time the API makes requests, the request is directed to the back end defined by the endpoint URL provided. Even if the API has multiple gateways, all the gateways directs the requests to the same back end of the defined URL as the following figure depicts.



Problem :

Assume a situation like this,

Person A designs an API with the endpoint <https://backend-region-1:8280> and works with it. Person B, which is in another region, <https://backend-region-2:8280> with the same back end database needs that API for some purpose. He deploys the API exported by Person A in the gateway of his region and try to use. But the API will never connect with the back end of his region. But in this situation, the API doesn't get connected with the back end of region-2. As the endpoint which the Person A entered is for region-1 back end only.

If an already designed API needs to be connected with a back end(same one) with a different endpoint(region) other than the already defined endpoint in the API, the API won't be able to connect with it. Simply, a designed API cannot be deployed in a region with a different back end URL (not a different back end).
 
Solution :

The proposed solution is to enter a dynamic endpoint at the time the API is designed. This endpoint should only be resolved at the run time so the API so the gateway would point a dedicated back end. This also applies when an API has more than one gateway.









_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Reply | Threaded
Open this post in threaded view
|

Re: [APIM] [C4] [2.1.0] API Gateways with Dedicated Back Ends

Akila Amarasinghe
Hi all, 

Sorry for the mistake. This is not the complete mail. The complete mail will be sent.

Thanks,

Akila Aroshana
Software Engineer (Intern)
WSO2

Mobile : +94702178247

On Wed, Dec 6, 2017 at 5:22 PM, Akila Amarasinghe <[hidden email]> wrote:
Hi all,

WSO2 API manager currently provides the facility for the user to input a single endpoint to the API when designing it. So every time the API makes requests, the request is directed to the back end defined by the endpoint URL provided. Even if the API has multiple gateways, all the gateways directs the requests to the same back end of the defined URL as the following figure depicts.



Problem :

Assume a situation like this,

Person A designs an API with the endpoint <https://backend-region-1:8280> and works with it. Person B, which is in another region, <https://backend-region-2:8280> with the same back end database needs that API for some purpose. He deploys the API exported by Person A in the gateway of his region and try to use. But the API will never connect with the back end of his region. But in this situation, the API doesn't get connected with the back end of region-2. As the endpoint which the Person A entered is for region-1 back end only.

If an already designed API needs to be connected with a back end(same one) with a different endpoint(region) other than the already defined endpoint in the API, the API won't be able to connect with it. Simply, a designed API cannot be deployed in a region with a different back end URL (not a different back end).
 
Solution :

The proposed solution is to enter a dynamic endpoint at the time the API is designed. This endpoint should only be resolved at the run time so the API so the gateway would point a dedicated back end. This also applies when an API has more than one gateway.










_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Reply | Threaded
Open this post in threaded view
|

Re: [APIM] [C4] [2.1.0] API Gateways with Dedicated Back Ends

Nuwan Dias
Hi Akila,

The subject of the mail is not descriptive enough for the feature we're trying to develop. What we're actually trying to achieve here is the ability for an API to be moved across environments without having to change the Endpoint URL. Basically Dynamic Endpoints to Enable CI/CD for APIs.

Thanks,
NuwanD.

On Wed, Dec 6, 2017 at 5:26 PM, Akila Amarasinghe <[hidden email]> wrote:
Hi all, 

Sorry for the mistake. This is not the complete mail. The complete mail will be sent.

Thanks,

Akila Aroshana
Software Engineer (Intern)
WSO2

Mobile : <a href="tel:+94%2070%20217%208247" value="+94702178247" target="_blank">+94702178247

On Wed, Dec 6, 2017 at 5:22 PM, Akila Amarasinghe <[hidden email]> wrote:
Hi all,

WSO2 API manager currently provides the facility for the user to input a single endpoint to the API when designing it. So every time the API makes requests, the request is directed to the back end defined by the endpoint URL provided. Even if the API has multiple gateways, all the gateways directs the requests to the same back end of the defined URL as the following figure depicts.



Problem :

Assume a situation like this,

Person A designs an API with the endpoint <https://backend-region-1:8280> and works with it. Person B, which is in another region, <https://backend-region-2:8280> with the same back end database needs that API for some purpose. He deploys the API exported by Person A in the gateway of his region and try to use. But the API will never connect with the back end of his region. But in this situation, the API doesn't get connected with the back end of region-2. As the endpoint which the Person A entered is for region-1 back end only.

If an already designed API needs to be connected with a back end(same one) with a different endpoint(region) other than the already defined endpoint in the API, the API won't be able to connect with it. Simply, a designed API cannot be deployed in a region with a different back end URL (not a different back end).
 
Solution :

The proposed solution is to enter a dynamic endpoint at the time the API is designed. This endpoint should only be resolved at the run time so the API so the gateway would point a dedicated back end. This also applies when an API has more than one gateway.












--
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
Phone : +94 777 775 729

_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture