Library Usage

Lura is presented as a Go library that you can include in your own Go application to build a powerful proxy or API gateway.

Of course you will need Go installed in your system to compile the code.

Several implementations are included in the examples folder to get you started. If you’d like to see a real-world example (using gin), see KrakenD Community Edition, which uses Lura to its fullest extent.

A ready-to-use example:

    package main

    import (


    func main() {
        port := flag.Int("p", 0, "Port of the service")
        logLevel := flag.String("l", "ERROR", "Logging level")
        debug := flag.Bool("d", false, "Enable the debug")
        configFile := flag.String("c", "/etc/lura/lura.json", "Path to the configuration filename")

        parser := config.NewParser()
        serviceConfig, err := parser.Parse(*configFile)
        if err != nil {
            log.Fatal("ERROR:", err.Error())
        serviceConfig.Debug = serviceConfig.Debug || *debug
        if *port != 0 {
            serviceConfig.Port = *port

        logger, _ := logging.NewLogger(*logLevel, os.Stdout, "[LURA]")

        routerFactory := gin.DefaultFactory(proxy.DefaultFactory(logger), logger)


Lura Releases

See the Releases list for the full list and changelog of Lura versions.


This section describes the philosophy and architecture used in Lura.

The Lura rules

  • Reactive is key
  • Reactive is key (yes, it is very, very important)
  • Failing fast is better than succeeding slow (say it one more time!)
  • The simpler, the better
  • Everything is pluggable
  • Each request must be processed in its request-scoped context

The big picture

Lura is composed of a set of packages designed as building blocks for creating pipes and processors between an exposed endpoint and one or several API resources served by your backends.

The most important packages are:

  1. the config package defines the service.
  2. the router package sets up the endpoints exposed to the clients.
  3. the proxy package adds the required middlewares and components for further processing of the requests to send and the received responses sent by the backends and manages the connections against those backends.

The rest of the framework packages contain some helpers and adapters for complementary tasks, like encoding, logging, or service discovery.

The config package

The config package contains the structs required for the service description.

The ServiceConfig struct defines the entire service. It should be initialized before using it to ensure that all parameters have been normalized and default values have been applied.

The config package also defines an interface for a file config parser and a parser based on the viper library.

The router package

The router package contains an interface and several implementations for the Lura router layer using the mux router from the net/http and the httprouter wrapped in the gin framework.

The router layer is responsible for setting up the HTTP(S) services, binding the endpoints defined at the ServiceConfig struct, and transforming the http request into proxy requests before delegating the task to the inner layer (proxy). Once the internal proxy layer returns a proxy response, the router layer converts it into a proper HTTP response and sends it to the user.

You can easily extend this layer to use any HTTP router, framework, or middleware of your choice. Adding transport layer adapters for other protocols (Thrift, gRPC, AMQP, NATS, etc.) is possible. As always, PRs are welcome!

The proxy package

The proxy package is where most of the Lura components and features are placed. It defines two necessary interfaces, designed to be stacked:

  • Proxy is a function that converts a given context and request into a response.
  • Middleware is a function that accepts one or more proxies and returns a single proxy wrapping them.

This layer transforms the request received from the outer layer (router) into a single or several requests to your backend services, processes the responses, and returns a single response.

Middlewares generate chained custom proxies depending on the workflow defined in the configuration until each possible branch ends in a transport-related proxy. All of these generated proxies can transform the input or even clone it several times and pass it to the next element in the chain. Finally, they can also modify the received response or responses, adding all kinds of features to the generated pipe.

Lura provides a default implementation of the proxy stack factory.

Middlewares available

  • The balancing middleware uses a strategy for selecting a backend host to query.
  • The concurrent middleware improves the QoS by sending several concurrent requests to the next step of the chain and returning the first successful response using a timeout for canceling the generated workload.
  • The logging middleware logs the received request and response and the segment execution duration.
  • The merging middleware is a fork-and-join middleware. It is intended to split the process of the request into several concurrent processes, each one against a different backend, and to merge all the received responses from those created pipes into a single one. It applies a timeout, as the concurrent one does.
  • The http middleware completes the received proxy request by replacing the parameters extracted from the user request in the defined URLPattern.

Proxies available

  • The http proxy translates a proxy request into an HTTP one, sends it to the backend API using a HTTPClientFactory, decodes the returned HTTP response with a Decoder, manipulates the response data with an EntityFormatter and returns it to the caller.

Other components of the proxy package

The proxy package also defines the EntityFormatter, the block responsible for enabling a powerful and fast response manipulation.