What is a reverse proxy in Apigee?

A reverse proxy is a server that intercepts all requests to one or more services and forwards them to those services.

This can be used for security purposes, for load balancing, or for any number of other reasons. In this post we will use a reverse proxy to make our application available over HTTP/2.

In the next section we will take a look at a simple example of using the Apigee Proxy service to make a simple service available over HTTP/2. In the last section we will take a look at a more complex example where we will create a proxy that not only forwards requests to a backend service but also adds authentication to the request.

For simplicity we will use a Node.js application that will act as our backend. In the next section we will take a look at a simple example of using the Apigee Proxy service to make a simple service available over HTTP/2.

Using the API Gateway. We will use the API Gateway service to forward requests from the frontend to our backend API. You can find more information about the API Gateway service here. For our example we will assume that you have already created your API in the Apigee portal. The API has a "backend" section where you can add a Node.

Now that we have an API we can use the API Gateway service to route requests to the API. In the API Gateway service there are a number of APIs that you can use. We will use the HTTP/2 version of the API.

Once the API is added to the API Gateway, it will generate a "VirtualHost" and a "Proxy". The VirtualHost will forward requests to the Proxy. The Proxy will forward requests to the backend application. Here is an example of the VirtualHost:

Once the VirtualHost is added to the API Gateway, you will be able to add a URL to it. In our example we will add a request URL for an endpoint of the backend application.

Next we need to add our Proxy service to the API Gateway. Once the Proxy service is added, we will be able to add a URL for the Proxy service. In our example we will add a URL for the URL of the Proxy service.

How to clone Apigee proxy?

In my previous posts, I explained how to get a copy of Apigee deployment.

Today, we will understand how to clone that proxy. If you want to know more about cloning proxy, you can check my previous post: Let's start! In this article, we will learn the process to clone a proxy by using Apigee REST API and command line. #1 Create an environment variable, APIID and APIKEY for REST API and CLI. #2 Create an Apigee deployment #3 Get the REST API ID, ID and API KEY #4 GET the deployment info #5 Clone the deployment #6 Update the clone (for new features) #7 Remove it (for deprecate features) #8 Update the clone (for new features) In Apigee, we have two environment variables for REST API and CLI: APIID and APIKEY. The APIID is always required, but the APIKEY should be provided if you are using a proxy with authentication. If you don't have the APIKEY, you cannot clone the deployment. So, create them first.

APIID=xxxxxx APIKEY=xxxxxx #2 Create an Apigee deployment. Next step is to create an Apigee proxy deployment. You need to specify a URL for proxy, a name for the proxy and its name for proxy resource. We also have another optional parameters for specifying the user agent, language and the location of a proxy, which is really good for making proxy easily customizable. The format of the apiproxy is:

Apiproxy=. In this example, the username and password is not encrypted. For an example, you can refer to the source code of this post: apigee-proxy-deployment.zip.

Note that you need to provide the username and password, not the password alone because of the usage of BASIC authentication. For the parameters, you can use the following format: apigeeproxy.

What is the difference between API proxy and API Gateway?

Is it the same product?

How does that work and what's the difference? Or are they part of a single product (?)

What's an API proxy? When your application requests data from the internet, there's an obvious choice of technology for how to handle that request and provide the response. You could have an in house solution, or you could go to an existing vendor who has already 'got it'.

The difference between an in house solution or vendor-based offering is the level of 'billing' for services provided to your organization. You may want to have a low cost entry point to external API's with a reasonable level of risk but no real visibility into the technical aspects of the process. This is an easy-start, low cost option for simple requests - if you want to get going.

If you plan to add more services later on and your budget has a 'reasonable' budget then maybe you need to go to a different model. The most common options for this sort of entry point are a REST client proxy or an API gateway. I like REST client proxies because they're low cost and easy to get going - but they come with very limited functionality - unless you pay for a premium package. Why would we use API Gateways? There's been a shift towards API Gateways recently as vendors realise the huge potential for value add to be had on top of the relatively small investment required to get the basics running. It allows customers to focus on their core technology while still delivering good business metrics on their revenue.

Why would we use an API Gateway, other than the obvious business benefits? The real differentiator here is the API Gateway model of billing for the services on offer. You can either pay a fixed amount or you can pay for the service as a variable usage - depending on your preferences.

This is an advanced topic (as expected for a blog post) and I'll take a deeper dive over the next few days but in short here's the top 6 differences between API gateways and traditional REST clients. They act as a single service. The REST client proxy is only interested in the data returned from the target API.

How to set up a proxy on Apigee?

This tutorial explains how to set up a transparent proxy service for an API Gateway for a Java based project.

The method shows how to set up a basic proxy configuration. This includes adding a basic auth handler, enabling dynamic authorization and setting up the response policy to allow some HTTP responses on the proxy service. For more information see:

For complete working example please see this link: Tutorial. First you need to setup an API Gateway. To do so we use Apache Tomcat 9 as Java container and provide it with a JDBC connection to an external Cassandra server. You can use Tomcat's embedded database instead of Cassandra directly if you like. Also, feel free to use one of many other container implementations out there.

TOMCATHOME = /usr/local/tomcat9-2.0.jar -c tomcattestconfcontext.xml, tomcattestconfserver.jar -Dcassandra.host=localhost -Dcassandra.port=8090 -Duser.name=admin -Duser.password=admin -Ddatastore.name=cassandra-service

Now we configure the HTTP proxy server on Apache Tomcat.