3scale API Manager using Load Balancer for API Gateways

  • You can deploy API Gateways inside your corporate network closer to your API and then have a Load Balancer in your DMZ (which is registered with API Manager) handling all the load and hiding your API Gateway to the outside world for high performance and to avoid single point of failure.
  • Another case is where API Gateway is installed via Docker containers and you want to have a Load Balancer handle the requests and forward to Docker containers.
  • You can as well use OpenShift (K8s) scaling feature to run the desired number of API Gateway PODs and have the OpenShift’s Route feature take care of Load Balancing functionality.
  1. Setup 3Scale API Manager either on SaaS or OCP.
  2. Create a Backend and Product for default Staging / Production API Gateway and check if you are able to call API or not.
  3. Setup Project (Namespace) on OCP for installing 3scale API Gateway Operator.
  1. Install “Red Hat Integration — 3scale APIcast gateway” Operator
  2. Deploy FIRST instance of self managed API Gateway
  3. Deploy SECOND instance of self managed API Gateway
  4. Configure OCP Route for Load Balancing URL
  5. Configure 3scale Product using the Route LB URL
  6. Promote your Product API to use LB URL at Staging API Gateway.
  7. Test the API using CURL.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store