KrakenD 1.0 is here!. Read our announcement.

Recent changes

Edit this page

Sequential Proxy

The best experience consumers can have with KrakenD API is by letting the system fetch all the data from the different backends concurrently at the same time. However, there are times when you need to delay a backend call until you can inject as input the result of a previous call.

The sequential proxy allows you to chain backend requests.

Chaining the requests

All you need to enable the sequential proxy is add in the endpoint definition the following configuration:

"endpoint": "/hotels/{id}",
"extra_config": {
      "github.com/devopsfaith/krakend/proxy": {
          "sequential": true
      }
  }

When the sequential proxy is enabled, the url_pattern of every backend can use a new variable that references the response of a previous API call. The variable has the following construction:

{resp0_XXXX}

Where 0 is the index of the specific backend you want to access ( backend array), and where XXXX is the attribute name you want to inject from the previous call.

Example

It’s easier to understand with the example of the graph:

KrakenD calls a backend /hotels/{hotel_id} that returns data for the requested hotel. When we request for the hotel ID 25 the backend service responds with the hotel data, including a destination_id that is a relationship identifier. The output for GET /hotels/25 is like the following:

{
  "hotel_id": 25,
  "name": "Hotel California",
  "destination_id": 1034
}

KrakenD waits for the response of the backend and looks for the field destination_id. And then injects the value in the next backend call to /destinations/{destination_id}. In this case the next call is GET /destinations/1034, and the response is:

{
  "destination_id": 1034,
  "destinations": [
      "LAX",
      "SFO",
      "OAK"
    ]
}

Now KrakenD has both responses from the backends and can merge the data, returning the following object to the user:

{
  "hotel_id": 25,
  "name": "Hotel California",
  "destination_id": 1034,
  "destinations": [
      "LAX",
      "SFO",
      "OAK"
    ]
}

The configuration needed for this example is:

"endpoint": "/hotel-destinations/{id}",
"backend": [
    { <--- Index 0
        "host": [
            "https://hotels.api"
        ],
        "url_pattern": "/hotels/{id}"
    },
    { <--- Index 1
        "host": [
            "https://destinations.api"
        ],
        "url_pattern": "/destinations/{resp0_destination_id}"
    }
],
"extra_config": {
    "github.com/devopsfaith/krakend/proxy": {
        "sequential": true
    }
}

The key here is the variable {resp0_destination_id} that refers to destination_id for the backend with index 0 (first in the list).

Unresolved issues?

The documentation is only a piece of the help you can get! Whether you are looking for Open Source or Enterprise support, see more support channels that can help you.