WSO2 APIs: External Vs Internal Gateway Implementation
The article following describes two different approaches to deploying the internal and external WSO2 gateway in the AWS environment, with their pros and cons.
WSO2 supports multiple gateway deployment patterns when we must set up a separate external and internal gateway to the server to traffic for external and internal consumers. The article following describes the approach to deploy the internal and external WSO2 gateway in the AWS environment.
Architecture
Possible Approaches
1. Using different EC2 instances for both internal and external gateways:
Process: New EC2 instances need to be created.
To serve within the AWS network, internal DNS will be needed and LB is not required.
Then GW service will be deployed over internal DNS and required PORT opening and listener configuration to be in place.
Finally, we will need to request for a DNS record to be used by internal customers and record data mapping should be done.
Pros
High availability will also be there even if other instances go down.
No impact will be there on the internal GW setup and vice versa.
Cons
The cost will increase by at least double.
The entire setup needs to be done freshly which will be a time-consuming activity.
2. Using the same EC2 instance for both internal and external gateways:
Process: A new Internal DNS is created while an LB is not needed.The
The same WSO2 GW service, which is in use by the external GW, will be deployed over 2 separate containers in the existing EC2 instance.
The same ports can be used, but connectivity needs to be established.
Need to order the new DNS and record data mapping so they connect similarly.
Pros
By utilizing the same EC2 instance, the cost can be optimized.
Setup can be completed quite fast as compared to the other approach.
Cons
Less availability and scalability compared to the other approach.
Topics:
wso2,wso2 api manager,gateway application,gateway implementation,aws,aws api gateway,aws devops
Comments